Personally, I just like the design of Zen more. With Firefox I felt like I was stuck with the same old UI forever. I'm not sure what Mozilla was doing with those bags of money from Google. I imagine Arc managed to do a lot more with their browser with way less money than Mozilla.
No it hasn’t, middle managers are the ones telling everyone below them to use AI as much as possible, even if it makes no sense and screws things up. AI is a middle manager’s dream.
Yes, this is what I meant. There hasn't been much news on it for some reason, but in Microsoft at least they're getting pushed out of their role, either to some more direct role, or out.
>The building of the software happens trivially now. You do not need a software engineer, sorry guys.
This part is quite "load-bearing".
I heard from someone who worked at Lovable that what most customers produce with that magical textbox is software that shouldn't go anywhere near production. Apparently the problem of thinking like an engineer is not solved by these AI tools. Most people who are not software engineers by trade are not capable of verifying what they produced, nor would they even consider needing to.
No offence, I think you might be a classic case of "senior who forgot how it feels to be junior", where after a lot work experience deva start taking their software engineering instincts for granted and forget that they are a skill that takes years to master. You can prompt an AI for a solution, you can even prompt it for ideas, but you cannot prompt it to think for you.
It's a markup language for documents. If you enable templating devs are then going to ask for more. Eventually it will end up turing complete. Such is the development arc of a lot of languages.
It's a repeated observation that keeps coming true. DSLs have a tendency to become turing complete over time.
- It happened to wikipedia's templating language
- It happened to PHP
- It happened to mod_rewrite
- It happened to server-side includes
- etc...
It just keeps happening.
In fact it's such a problem with infrastructure teams that use yaml/json configs that you see a lack of turing-completeness being advertised as a feature (see Dhall configuration language).
I don't disagree with "DSLs have a tendency to become turing complete over time", it's a well known fact.
But "we can't give something to users because otherwise they'll ask for other stuff" is not an argument. They're _already_ asking for stuff (templating) anyway. No one is suggesting that shutting users up is a reason to implement templating, it's the trade-offs of this feature that are debated. And if it gets implement then yes, users will certainly ask for more features, the trade-offs of which can be debated.
If you think that the line for HTML features is where we already are, you can present your arguments for why (tbh I'll probably agree). But "if you enable templating devs are then going to ask for more" isn't one.
The reality is that 90% of the features they ask for boils down to adding just a simple if statement, and as soon as a DSL has a practical if statement it becomes turing complete.
If the other 10% of features are implemented, then any further change makes the DSL turing complete.
It's not even really `if` by itself, conditionals are good enough. Templates with for loops that can check if an index is the first or last can implement if statements. Also templates that can nest other templates recursively with a max recursion depth can also implement if.
You have to go out of your way to avoid turing completeness if you want to avoid a complexity explosion.
It's almost a meta-slippery-slope fallacy, in that the specific slope is not specified; only the existence of the slope and its slipperiness is asserted.
The slope we've observed over the decades is PHP. Which went from "basic HTML templating language" to "dotnet but you write $ everywhere". PHP has grown so much in complexity and feature-set that Symphony and the likes are legitimately dotnet-type. They make Go backends look low-level and primitive.
Windows desktop native is WinUI 3 and Windows App SDK, for better or for worse. No amount of Rust and tokens will recreate everything you get out of the box with that stack. Native needs to feel native.
The last time Windows UI felt native was maybe Windows XP. Maaayyybe 7, if we are generous. It also has to do with sluggish or no feedback by UI widgets, due to the trend of flat everywhere.
Point wasn't about fixing the exact issues, the point was how it even got that bad. Of course the easiest route to comprehending the complaint by Bill is to immediately fix the specified issues, making Bill a simple QA instead of concerned leader.
I think accountability would involve trying to understand how it got that bad, and figuring out a new process for preventing it from happening again. Though I'm sure that never happened.
In my humble opinion, some of the blame has to land on Bill himself as he has the full power and agency to build a style of management in his company that would've prevented this from happening. Instead he just scolded a bunch of senior execs who usually find a way to just delegate some work to tuck away any visible issues and go on with their merry lives.
reply