skysight-inc/HackerNews huggingface dataset:
Multiple inheritance and SFINAE through templates are the only non-concept way of doing traits in C++

The way single inheritance is used in C++ is nothing like how traits are used in Rust.
America Is Backsliding Toward Its Most Polluted Era
I've seen a number of startups who are stuck on .NET Framework, simply because some affordable agency built them an MVP with ASP.NET a while ago and it worked (TM) to get the business going.

Then someone like me gets called into a situation where they have ridiculous hosting costs (Windows-only, typically also MS SQL), nasty performance issues, and struggle to stay productive and find developers. The most reasonable path forward I see in those situations is a gradual migration to .NET Core and something like PostgreSQL.

And that's a major investment. Microsoft couldn't have made .NET Framework code harder to port to .NET Core if that had been their explicit goal. I find database migrations with Entity Framework similarly difficult compared to other ORMs. Startups can sometimes afford such investments, but often not.

And that's how you ironically get 2-3 year old startups stuck on a death march old school enterprise code stack. It appears to be more common than I'd like it to be.
Spring Boot 3 requiring Java 17 is what allowed the migration in two companies I’ve been, it’s much easier to sell it as security issue than tech debt.
> lets remove them

How?
Vermin Supreme: It’s happening!
Europe's AI Leadership with an Ambitious AI Continent Action Plan
This is also why reports from StackOverflow on language usage should not be considered to represent the entire software development market, more so whats popular, new and open source.
What about spam filters? Both for incoming mail as well as your ability to not get flagged.
Las Vegas: How the internet's most notorious risk-taker always wins in the end
Support for .NET Frameworks 4.8 is essentially forever and .NET Core requires you to jump one version up almost every year, which has a much higher maintenance cost.
This generates a random password that can be shared via a one-time link. Why? What is the situation where this would be used?
> Why should I hire you if an agent can do it ?

An agent can't do it. It can help you like a calculator can help you, but it can't do it alone. So that means you've become the programmer. If you want to be the programmer, you always could have been. If that is what you want to be, why would you consider hiring anyone else to do it in the first place?

> Spotify CEO stated on X that before asking for more headcount they have to justify not being able to do the job with an agent.

It was Shopifiy, but that's just a roundabout way to say that there is a hiring freeze due to low sales (no doubt because of tariff nonsense seizing up the market). An agent, like a calculator, can only increase the productivity of a programmer. As always, you still need more programmers to perform more work than a single programmer can handle. So all they are saying is that "we can't afford to do more".

> The company will and is just using the agent as well …

In which case wouldn't they want to hire those who are experts in using agents? If they, like Shopify, have become too poor to hire people – well, you're screwed either way, aren't you? So that is moot.
It’s not a wide spread “problem”. It’s just education lagging behind technology.
Apotris is the funnest version of this that I’ve played. I have it on an R36s and also on my iPhone via emulation. Works better with native controls but still fun on the phone.
Hot take: CSS is actually type safe, just doesn't get compiled & fails gracefully ;P
> Porting .NET framework to .NET core / standard / 6+ really isn't as smooth as MS would like you to believe.

Having just spend the better part of 3 months porting a lot of legacy projects, you're absolutely right, but I am not sure where MS said this would be smooth. There are some processes that are standard enough but certainly there is a lot of hands on work involved, and actually for good reason, there are performance and security issues that need to be addressed (In my brief, and hopefully final experience).

That said, porting from event .net versions (stable LTS versions) such as 6 -> 8 has so far been flawless, I think over the last year, we ran into maybe some minor semantic issues.

It's not perfect, but I have to defend MS unfortunately, they are taking things in the right direction while being tied to a LOT of legacy enterprise clients and systems.
FWIW, I got what labster and understand why you commented.

But what I do not know is why the down votes ? To me, both of you seems to agree with my intent, am I missing something ?
> It's not up for debate. Ask any programmer if LLMs improve productivity and the answer is 100% yes.

Programmer here. The answer is 100% no. The programmers who think they're saving time are racking up debts they'll pay later.

The debts will come due when they find they've learned nothing about a problem space and failed to become experts in it despite having "written" and despite owning the feature dealing with it.

Or they'll come due as their failure to hone their skills in technical problem solving catches up to them.

Or they'll come due when they have to fix a bug that the LLM produced and either they'll have no idea how or they'll manage to fix it but then they'll have to explain, to a manager or customer, that they committed code to the codebase that they didn't understand.
It's interesting to learn that this means "language of the Franks"

I've always thought it meant more "language of the francs (old french currency)", ie "the language of doing business"

Learn something new every day
"Retailers mark up the shoes 100% to recoup various costs and generate a profit."

Whenever I enter any physical store it always boggles my mind how insanely inefficient the whole endeavor is for all involved. But that retail basically swallows half of the price is just unbelievable.
That has to be one of the best comments I've read on here in a while.. a nice chuckle for the morning.
Boomers really fucked on the economy to Sunday didn’t they?
I live in northern county and can vent my 3d printers exhaust to the outside. Friend of mine from CPH did the same with his resin printer.

And if you actively went it outside carpet and close proximity should ok ok'ish health wise. It's just effort and noise that a lot of people don't like to put in.
Trump has alzheimers dementia. That's not some general kind of madness, it's a genetic degenerative brain disease.
Well you're really helping the sitch here, ain'tcha…
Because they trained them on Vloggers and TikTokkers and Podcasters without asking any of them permission.
The problem with Java migrations is sometimes people (ab)use the behavior of a specific library in that specific version, and when you change the runtime, everything comes crashing down (visibly or invisibly).

I have seen quite a few Java applications which fails at unrelated points, and every time I have been told that the thing only runs with "jre-old.very.specific.version-and.point.release". Otherwise you're out of luck.
The OS support isn't quite as ironclad as that. Windows Server 2019 was the last version where .NET Framework 3.5 will be supported for the lifetime of the OS; while later versions still include 3.5 as an optional feature, it's only going to be supported until January 2029 (when 2019 goes out of support), even if the OS is still in support.

We know .NET Framework 4.x will still have to be supported through October 2034 to meet similar support obligations for Windows Server 2025; but Microsoft could easily let that be the end date for 4.x if they wanted, even if Windows as a whole is still supported.
Well, LLMs aren't just randomly spitting out garbled text either. Humans create and curate the training data, humans design the models, and humans train them.
The horrible naming thing is epitomised by the frankenstein that is, "ASP.NET Core 2.3", which is a re-release of "ASP.NET Core 2.1", which is actually a .NET Framework thing.

Re-released because ASP.NET Core 2.1 had a better support lifecycle than ASP.NET Core 2.2, and people "upgraded" to 2.2 not realising this.

So people got stuck on unsupported 2.2, rather than the supported 2.1.

So they re-released 2.1 as 2.3, to give people an "upgrade" path from 2.2 to 2.1.

All named after "ASP.NET Core" which, confusingly, is detached from ASP.NET on .NET Core.

( .NET Core which is now just ".NET" , of course. )

Read the whole horror-show here: https://devblogs.microsoft.com/dotnet/servicing-release-advi...

I swear .NET has had the best technology focus for the past 5 or so years, but has had absoultely the worse brand and a complete lack of developer relations / brand ambassador type work.

They need someone who can turn around and tell them to stop this madness, and focus on getting out that .NET is a fantastic ecosystem that performs damn well, and modern C# a pleasure to write in.

But instead we get stuff like "EF Core 9" that targets .NET 8, and all the 9.0.x system libraries, where isn't not clear whether you should be using them if you want to stick to the LTS and target .net 8.
If I’m writing in an unfamiliar language or using an unfamiliar library, I will mostly have several browser tabs opened. That’s because the docs usually have caveats and other tips that will be missing from LLMs. And a book can do wonders for strengthening your foundations.
Eating the big fish is one great book about competing with a market leader. You're talking like go to market is rocket science. Anyone can read a book and follow the steps. Many don't.
Executive orders are not laws, they're fancy memos. Puerto Rico is in the US btw where the official language is also Spanish.

https://en.wikipedia.org/wiki/Languages_of_the_United_States

> On March 1, 2025, President Donald Trump issued Executive Order 14224 to symbolically designate English as the official language of the United States for the first time.[2][23] The U.S. Congress has never passed legislation declaring an official language at the federal level,[24][25] but English is typically used by the federal government and in states that do not have an official language.
> Why should I be bothered to read what nobody could be bothered to write?

In an art-criticism sense I broadly agree with you, but I think you go too far from a reader-experience point of view.

> The point of writing is communication and creative writing is specifically about the human experience

That's a point of writing, but the point of reading is only sometimes about communication. It's also about entertainment, enrichment, or expressing half-formed thoughts and feelings.

Take a step back from the autonomously-written novel and imagine something a bit more collaborative. Many players of open-world-ish games develop an emergent story, what if that story could be semi-automatically novelized to document the unique narrative of the playthrough?

SimCity 2000 had "mad-lib" newspaper articles that commented on the city's status; consider ones written by an LLM with full knowledge of the game's state and context.

> something a LLM can mimic but never speak to authoritatively.

Supposing a reader can't tell the difference between an average human-written novel and an average LLM-written novel, where does this authority lie?
People still calligraph even though we have printer. People will actively spend money in a hobby they like. It's totally fair that you personally might not want to do it anymore if AI can, but I think parent was saying other people will continue to do it if they enjoy it. There are tons of people who create copy right free music anyways. Talking about those type of people. :)
Bait Hook Reward Payload
Now I'm really curious what ??? will turn out to be :-D
There are newer design with foldable pins. Other than size I dont see anything you mentioned as downsides. Especially Earth Pin.
> It hurts to listen to.

Does it really? Isn’t this the kind of thing it would be good to practice tuning out rather than complaining about?
Off the top of my head, I would imagine transplanting gives more control over the end result.
I found the idea of polling DB queries interesting. They basically took what is done with HTTP and pushed it down the stack directly in the DB server, eliminating the extra SQL round trips one needs to make server-side in order to provide updates. Neat!
I suspect a non-small part of the story is accounting rules. If you're in a place where such an upgrade would be paid for out of operational expenditure, there's always going to be a reason not to do it.
To be fair, that is not problematic at all and most definitely not what I think is the issue with Nix adoption/learning curve.

Personally, it's the fact that there are 57698 ways of doing something and when you're new to Nix you're swarmed with all the options and no clear way of choosing where to go. For example, the docs still use a shell.nix for a dev shell but most have moved to a flake-based method...

I always recommend starting with devenv.sh from the excellent Domen Kozar and then slowly migrating to bare Nix flakes once you're more accustomed.
this is the way. Modern CSS brings most of the capabilities to the table that SASS & LESS used to provide, and in part even much more functionality that could never be adequately solved with preprocessors (runtime calc(), light-dark() and layers come to mind)

I'm still a fan of LESS, but quite specifically because it _does not_ try to force another languages syntax into my preprocessed stylesheets, rather keeps everything as css-like as possible. This makes it much easier to transition things to vanilla-only when possible, absolutely dreading "mostly js"-types of SASS frameworks
They were dyed, rather than painted. The details come from the photograph.
Elliptical Python Programming
It depends on the country. There are many countries where oral antivirals are available OTC.

To say this drug is prescription-only is plainly not true.
It's a database that emphasizes stored procedures. And if you need it to distribute computing, it has the same challenges as the eliminated "game servers".

In addition, outside of single table updates and selects, SQL has scaling limits. If you throw the computation at the db server as well, you limit the vertical scaling.

Gaming and gamers are used to sharding (and geographic tower of babel us an implicit shard as well).
So, what were the showerhead regulations prior to this repeal? The article doesn't expend even a single word to inform us.

Edit: WaPo is less useless: The order, first reported by the Wall Street Journal, directs the Energy Department to rescind a regulation issued under President Barack Obama and later reinstated under President Joe Biden. The rule limited the flow from each shower head on the market to 2.5 gallons of water per minute.

https://www.washingtonpost.com/climate-environment/2025/04/0...
I am on macOS with a split screen browser left and emacs in the right half. Max 2 window vertical split in that frame and if needed a C-x 5 2 which opens a full screen frame workspace to the right for a c-x 3 side by side layout. That’s it - all the other buffers are backstage partying until they get called.
Re mental health - this is extremely interesting if it turns out to be correct. Thanks for sharing
> Looks like they've built stuff before.

Building "stuff" != shipping games.
Thanks for this post. I bought this model used in 2019 and still use it daily. Beautiful screen and form factor, a real gem. The updates stopped a long time ago.
You will be able to once you change your success indicator from profit to the simple joy of learning and making
But the country is polarized. So this woke/MAGA maximalist seesaw is what you’d expect if democracy was working.

The two-party angle really has very little to do with it, because there’s not that many “true moderates” in the electorate. Research shows that the “center” is comprised of people with a heterodox mix of views, but they’re not particularly mushy about any specific view.
bzlmod feels better at first but you're left navigating version conflicts anyways.

Vendoring deps is the only true real sane way for large repos
The discovery of fire itself was not progress, but how to use it very much is. They most likely didn't have a "discover fire" specialization in the modern sense but I doubt the one first to create a fire starter was afterwards deligated to only collect berries. The discovery and creation of something obviously often comes before the specialization or it would otherwise be impossible to discover and create anything.

>FWIW I don't have a microwave oven.

That was just an example. You still know how to use them hence basic knowledge. Seem like this discussion boils down to semantics
Our org seems to be taking some benefits from being sped up by using AI tools for code generation (much of it is CRUD or layout stuff), however at times I'm asked for help by colleagues and the first thing I've done is Googled and found the answer and gotten a "Oh right, you can google also" since they've been trying to figure out the issue with ChatGPT or similar.
Looking forward to giving it another try!
That's a nice start. Next thing I know he might give me a toilet that can flush one of my infamous Falcon Heavy's.
Does this make any sense in single-player games, where the db would run locally on the user's machine? Does it have any benefit to run all game state through a local db?

I'm not a game dev, but I'm imagining that if I'd write a custom game engine, I'd have to write just the "frontend" aka. graphics engine if I'd have a robust state manager (+tooling) as a separate piece of software.
Can we all accept the notion of feature-complete software?

It is easy if we take away employment incentives, promotion oriented work.
I noticed you mentioned email receiving in your landing. How does it work?
It’s an interesting observation that the structure of a piece can reduce its value regardless of the content. Not sure I agree, but interesting.
> Inventory cost doubles, perhaps now they have to take out higher interest debt to finance that.

I'm pretty sure Footlocker doesn't borrow money to pay Nike up front for inventory. Nike is smart enough to know that there's zero chance their shoes will be sold if they sit in a warehouse, so Nike might as well ship them to retailers and get paid gradually as the shoes are sold to consumers.
Additionally, their risk increases.

If the shoes don't sell, their losses can get much larger.

They need the potential to make more profit to offset this this potential for larger losses.

It's kind of like asking why Sears needs to make $200 in profit selling a refrigerator but only $2 selling a t-shirt.

Because that's just how it works...
> but I wonder: what are the security requirements then, if any?

None, mostly. You just get on the train.
At my workplace, we treat .NET 4.x as an enterprise runtime considering its widespread availability and good maintenance. While we design and compile all the modules with first-class support of new .NET versions, all of them are able to run on .NET 4.x as well. To make that possible, we use a handful amount of polyfills. Fortunately, it all works transparently without causing any troubles.
Migrated a small-ish project from ASP.NET Framework (.NET 4.8) to ASP.NET Core (i.e. .NET 8) including EF6 to EF Core last year. Even though it was pretty smooth sailing (the application was already using MVC), it was still a few weeks work.

Rewrite queries that are not yet supported on EF Core, create some new DTOs, create drop-in replacements for stuff that isn't there anymore, create plumbing to connect some old stuff to some new stuff. Figure out what's the new replacement for XYZ and use it correctly to not break anything. Replace nuget packages that are not maintained anymore or have so few downloads that they are a supply chain risk.

You need to test every endpoint, every query in your application.

And in the Microsoft World you're still pretty ok, overall, it's quite stable.

God forbid you put your money on the wrong web framework (not even talking frontend) in the Java space. There's still Tapestry/Struts/Grails/JSF/GWT/Play etc. applications serving your request out there. Saw some banking website with ".do" urls recently (indicative of Struts).

Unless we get superhuman AI that can do such migrations all on their own, those zombies might have a longer working life left than lots of developers. Many companies just can't afford to upgrade - there's so many systems built over decades that just do what they should do. Why shell out tons of money to just get the same functionality?
If a British tank's tea-making facilities aren't working, it's the same.
> .NET Core requires you to jump one version up almost every year,

Close.

* The requirement is to jump every second year when a LTS version comes out. Last one was .NET 6 to .NET 8. And next, .NET 10 will come in November 2025. You can jump 1 version every year, but it's not a "requirement".

* It's just called ".NET" now, not ".NET Core". There is no ambiguity in e.g. ".NET 8" - it's the modern version formerly known as ".NET Core".

* Release is every year in November, and every second one is LTS. there's no "almost", it's every time. IDK if this will still be so in 10 years time, but it's been consistent.

* maintenance cost? Yes, you have to review project files and build pipelines in order to to update, so there's some detailed work, but the actual breaking changes and puzzling issues are few to non-existent. It typically goes very smoothly after you change some numbers.
Seems like you'd still be doing that in a distant way, since it all began as human prose at the training stage.
> - Industry inertia — teams hesitate to rewrite working systems without a compelling business reason.

Isn't this how it should be?
True.

And … if there is a future at all.
You will be able to detect any AI music from human music because of the ability to detect this human element? Or are you saying you'll retroactively hate a song once you figure out it was AI generated?
No, small talk serves an important social function.
This is completely false and goes against the experience of the vast majority of the teams.

Using .NET Framework carries significant risk and opportunity cost. Updating LTS every 2 years usually comes with simply bumping up versions and rebuilding.
Come for the menial and absurd, stay for the flagrant anti-constitutional (in spirit) issues.
Their capital was named after a Texas city, no?
> .NET Core requires you to jump one version up almost every year, which has a much higher maintenance cost.

This is basically seamless now, the framework isn't changing in backwards-incompatible ways anymore.
Speed and scale of long-distance travel are obviously the relevant factors, not just "is it possible to go far".

Air travel is faster than horse, and carries more people.
I just want to mention it wasn't invented by Apple.
20b euros investment in this just one big tech company in the US for one year.

The report doesn't mention whether it will use Nvidia chips or something else. If they don't use Nvidia, and instead, choose to develop their own chips, they'll have something inferior, likely much higher cost, and longer time to usable datacenter.
The projects would be roughly the same, but information about them would be significantly cleaner

If I see an article about .NET, depending on the year it might be about 2 different product lines, because the shorthand was made to be the same

If I need to google how to X in Visual Studio, more than half of the results will be irrelevant, because they will be about a different product, so on and so on

If the naming was good, it wouldn't trip up people (So regularly at least), that's my point

Other ones that trip up people, Teams for personal use?, that one regularly bugs out when interacting with business users?
Skype vs Skype for Business?