2,144 karma · joined November 29, 2024
Sure, it's a valid language design, but it's also a negative in "understandability of each line of code", and thus maintainability, and even stuff like tooling, verification.
With all due respect yours is a very short sighted take that only thinks in passing tests. That's not the purpose of education.
> I don't know what would be a good career path, but most certainly avoid anything that AI is having the most success at in 2026.
This hinges on an assumption that means our whole society is turned upside down completely with no way to predict anything. But this is an assumption only. So you can either plan for a known path and do something valuable there, OR just put up your hand and prepare for.. what? Like not even physical jobs are safe because who will hire anyone if a good chunk of all humans will be out of jobs? Your best bet would probably be to build a bunker and stock up on canned food.
So unless there is a change towards UBI in your take (which is still not an all around solution. Many people only fit properly in a society because they are occupied 8 hours a day with something), that will probably result in the biggest revolution ever seen.
And there is not enough high walls to save the rich from that.
Until those who don't own capital get upset and put the whole thing on fire.
But I don't think this video was meant to cover this case, and in the more pessimistic predictions you are not better with any other profession either. Given his assumptions I think it is an absolutely fair take. If AI becomes better in all 4 areas of math he lists, then private funding may decrease - BUT if there is ever any need for human problem solving skills, academia will not break down and this has always been the majority where mathematicians are employed/financed from.
And if this latter assumption breaks, we are in far greater trouble than whatever you chosen as a career and society will become unrecognizable to today's.
Funnily enough kotlin added some rushed, delivered syntax sugar in the form of `when` and java just came and added proper pattern matching with algebraic data types and exhaustiveness checking into the platform itself, making it better than the guest language at its own game. Meanwhile I never felt this "landing page growing" mindset with Scala.
You really have to wrap your head around dependent types and _≡_. In my experience it was far more mind blowing than just FP.
Which of these is impressive or novel?
At the price of your passenger seats being occupied by gas tanks, that surely are safe in a collision that's far more likely occurrence.
It's PR stunt, nothing more.
I'm not saying that it's necessarily the case here, but typst is past the very early phase and LLMs are decent at generating it. Also, many formatting templates have been converted to typst as well.
You just have to remind the politicians from time to time - the French are a great example in that.
Also, it's a false equivalence - it's also easier to buy a walkie talkie, but that's also not replacing Android smartphones. "Gnu/Linux" userspace is simply not even close.
But do they? In my experience, at most workplaces it's simply a meat linter phase with the occasional useless comment about style (which should probably be handled by proper CI/CD).
Like if you don't even check out the code (generalized 'you'), then they can hardly build up that model. And even checked out, viewed in its proper context, Naur's famous paper comes to mind - the author who wrote it is the only one who has properly built the theory (which might have included alternative implementations that failed but have no visible artifact).
I'm not claiming that there are no places that go absolutely above and beyond with their review sessions, but I would argue it's really rare - and AIs are great at figuring out some of the context the PR description lacks.
If you mean executable formats, they're their own different things, it's just machine code wrapped OS-specially. I don't see how they are fundamentally different "from an app" - you also have a bunch of metadata in there and an entry point. Just because it's an XML file in Android's case which can just as well jump to machine code (you can have Android apps written in CPP/Rust whatnot), it's all just an implementation detail.
Well, do you mean xclock to draw over different windows/activities? Because that's just a different similarly to how Wayland is different from X -- it's generally frowned upon to not have a central entity manage who can draw where.
Otherwise, you can trivially do whatever you want, including drawing manually similarly to X's API, or using OpenGL or similar hardware accelerated apis.
And there are quite a few devices with unlockable bootloaders so you can feel to hack whatever you want with AOSPs.
It's not a technical problem, it's a social one (for the apps/programs)