The problem is, laptop companies don't "make laptops". They are big machines that puts parts together in the right configuration and call them "laptops". No thought goes into it. They are indistinguishable from any other deep pipeline of manufacturing, such as one that makes bicycles or refrigerators. New year, generate a new product ID, upgrade the CPU and RAM using the reference schematic provided by AMD/Intel, throw it in the ERP, make a BOM, and start rolling them off the assembly line.
What we see is a deep disconnect between visionaries and the companies that operate these deep pipelines. Apple has tried to maintain a connection between design and manufacturing by having great designers at the top (and other companies poach them).
A few daywalkers like Bunnie Huang walk both sides of the world.
Controversial opinion: Scala should have gone into maintenance mode a decade ago. They got the language right at the beginning, and a decade of tinkering has just fatigued everyone and destroyed any momentum the language once had.
Many of the Scala projects got people fired. Something the Scala devs largely ignore. Plus Scala support is truly awful even by the low standards of an OpenSource project. Then there is the fact that the Scala specific libraries are largely dead.
Scala had/has a lot of promise. But how the language is marketed/managed/maintained really let a lot of people down and caused a lot of saltiness about it. And that is before we talk about the church of type-safety.
Scala is a more powerful language than Kotlin. But which do you want? A language with decent support that all your devs can use, or a language with more power but terrible support and only your very best devs can really take advantage of. And I say this as someone writing a compiler in Scala right now. Scala has its uses. But trying to get physicists used to Python to use it isn't one of them. Although that probably says more about the data science folks than Scala.
PS The GP is right, they should have focused on support and fixing the problems with the Scala compiler instead of changing the language. The original language spec is the best thing the Scala devs ever made.
Kotlin has become a pretty big and complex language on its own so I'm not sure this is a good counterexample.
The fundamental issue is that fixing Scala 2 warts warranted an entirely new compiler, TASTy, revamped macros... There was no way around most of the migration pains that we've witnessed. And at least the standard library got frozen for 6+ years.
However I agree that the syntax is a textbook case of trying to fix what ain't broke. Scala 3's syntax improvements should have stuck to the new given/using keywords, quiet if/then/else, and no more overloaded underscore abuse.
One impressive thing for us is that the changes to macros were hardly an issue. We'd been trending off macro-heavy libraries for a while, and our Scala 3 adoption has not really been harmed by the new macro system.
> Scala had/has a lot of promise. But how the language is marketed/managed/maintained really let a lot of people down and caused a lot of saltiness about it. And that is before we talk about the church of type-safety.
On the contrary, there was nothing wrong with Scala's marketing. What's damaged it is a decade of FUD and outright lies from the people marketing Kotlin.
Are you still taking suggestions? You should have a "random recipe" button that loads something random from your database. Right now, your product is very one-dimensional: Someone has a specific problem, they find your solution, they use it. But, adding another dimension for people who don't have that problem is a good idea. And I think a random recipe button will naturally open you to finding what that second dimension is.
I can buy a smartphone or tablet that's 100% unlockable and has all the bells and whistles right now, and get it delivered in 24 hours, and not pay significantly more than average.
I think the market is working just fine. (To which people usually say "for now". Well yeah, the sun hasn't gone supernova... for now)
Yes, and heroin users can go buy fruits and veggies if they want to improve their health outlook. The fact that better alternatives exist does not mean the market will reward them, which is the point the parent is making.
This is cool, but reminds me of what we don't have. 99% of the content for Unreal Tournament was made by the community. Why can't the community make an open-source game? There are probably even attempts to make an open-source UT04. But I wish open-source could just make more standalone games. We have so few... Tuxracer, Chromium BSU, Battle for Wesnoth, Warsaw, etc.
That's easy to say. But they do prevent some cheating. Don't believe me? Consider the simplest case: No anti-cheat whatsoever. You can just hook into the rendering engine and draw walls at 50% transparency. That's the worst case. Now, we add minimal anti-cheat that convolutes the binary with lots of extra jumps and loops at runtime. Now, someone needs to spend time figuring out the pattern. That effort isn't free. Now, people have to pay for cheats. Guess what? Visa doesn't want to handle payment processing for your hacks & cheats business. So now you're using sketchy payment processors based out of a third-world country. Guess what else? People will create fake hacks & cheats websites that use those same payment processors, and will just take people's money and never deliver the cheats. You get to try to differentiate yourself from literal scammers, how are you going to do that? You can't put the Visa logo on your website. Because you're legit, and you don't want to get sued. Then, the anti-cheat adds heuristic detection for cheat processes. The anti-cheat company BUYS the cheats and reverse-engineers them and improves the heuristics. then the game company makes everyone sign up with a phone number, and permabans that phone number when they're caught cheating. Now some gamers don't want to risk getting banned. Saying that these factors simply don't exist or are insignificant is certainly one of the opinions of all time.
100% agree. This is exactly the kind of big picture thinking that so many people often seem to miss. I did too, when I was young and thought the world was just filled with black and white, good vs evil dichotomies
That is not always possible for genres with fast gameplay like most shooters. It's quite common for player movement to be able to put an enemy in view before the light could've round-tripped from the server.
This is generally the anti-cheat problem. Certain genres have gameplay that cannot be implemented without trusting the client at least some of the time.
This is correct, the correct amount of over-sharing by the server is non-zero, because otherwise you give a HUGE advantage for slight ping differences.
It's even worse, the lowest theoretical latency possible based on speed of light alone is not low enough for the speed of movement in many shooters, if the server hid all immediately invisible information.
What do you do with footsteps and other positional audio? On multiplayer shooter games that's very vital information to let you know an enemy is somewhere behind a wall but cheaters can use it to draw visual markers to pinpoint the enemy player.
I'm sure a lot of people are waiting for peak AI fatigue to jump in with a simple OS that is actually user-friendly and doesn't try to cram an "agentic AI" into your computer with you.
* The Deluge: 17th century double invasion of Polish-Lithuanian Commonwealth by Sweden + Russia.
* America has lost faith in Europe. Cold war is over, administration doesn't value European trade.
* American right is racist and no longer cares about democracy.
* Russia plans to invade Poland, Estonia, Latvia, Lithuania, Finland, and Moldova. Alleges that China is helping.
* Europe is facing another "deluge" because it's under attack on two fronts.
* Solutions: reindustrialize, remilitarize, cut pensions, befriend India.
Did I miss anything?
reply