Readit NewsLuckily, in the IT industry, it's common to just use first names with everybody.
Me too. There are still German companies where coworkers address others with Herr or Frau followed by their last name.
I find it also interesting how people that learn German understand the difference between the "you" in formal ("sie") and informal ("du") version, but often don't understand in which context du use them. In most cases you can use the informal "du" nowadays, especially when you are out with somebody for a beer.
After elementary school we had this interesting shift form addressing the other children with first name to addressing them with last name. We were circa 11 years old.
But once you don't use ORMs or have a non-monolithic architecture, you need something to validate your schema.
Lately, I used code agents a lot, and having typescripts types infered from Zod schemas allows me to catch errors when the large-language model generated slightly wrong code.
It boggles my mind how much effort and complexity and tooling goes into building an SPA. Entire classes of problems simply don't exist if you choose not to build an SPA. Meanwhile, I use the browser as designed: with full page reloads, backend development only, and occasional reactivity using a backend-only framework like Laravel Livewire. Everything is so simple: from access control to validation to state management. And yes, my app is fast, reactive, modern, SEO friendly, and serves thousands of users in production.
In the end you'll have a schema somewhere. Maybe defined in the database system, maybe defined in the models of an object-relational mapper. Since defining the schemas in database system or using object-relational mappers can cause very difficult problems in large projects we do not use it and use Zod and Protobuf instead. While I think you could even replace Protobuf completely with Zod or something similar.
There is the British Post Office scandal [1] around an IT system called Horizon (the legacy system in this case). After reading about the details I'm pretty sure something like Zod (I mean any schema validation) would have contributed to prevent this scandal. They even mentioned the lack of using a schema in the technical appendices in the court documents of the group legal action [2].
[1] https://en.wikipedia.org/wiki/British_Post_Office_scandal
[2] https://en.wikipedia.org/wiki/Bates_%26_Others_v_Post_Office...
What backs up this claim? And when will it reach it?
We could be very well reached a plateau right now, which means looking at previous trends in improvements does not allow us to predict future improvements. If I understand it correctly.
One of the most confusing things about the space is that you only learn after using every high-level editing library (Lexical, etc.) that ProseMirror really is the right abstraction, a masterpiece of engineering and architecture. The reason this is unintuitive is because ProseMirror is essentially the same level of abstraction as a compiler middle-end, and it's surprising that there are no higher-level abstractions that seem to work better in practice. If you are doing something remotely non-trivial, you will need the customization that only ProseMirror provides, and you will learn that the hard way. You will need the decade of bug-fixes for various touch devices and old browsers, you'll need the careful work that has gone into performance, and so on.
For a long time the missing piece was that (1) PM defaults are not what the vast, vast majority of users want, and (2) it is nearly impossible to get it to work cleanly with React. react-prosemirror, in my view, is the solution. Every day I am happy that I get to work with it, and I am not sure what we'd do without it.
As far as I know Meta's Lexical [1] (used by Facebook, Whatsapp, and Instagram) is goes also a similar direction: customizable, but it takes time to get used to it.
- heavy dependence on large (Mono) and/or unusual tools (nmake ... in 2024 ... really?)
- worse than that, dependence on specific (older) versions of exotic, non-standard things
- not much in the way of "this is what the language looks like" or "this is what this language is good at"
- the windows world smell surrounding the project is pungent, to say the least
I hope for the sake of the project this is a temporary state of affairs.
[EDIT]: a maybe slightly better intro to the language than the github page:
>Not too appealing to have to install that much crap on one's system just to play with a new language.
Ironically, this is what I thought about C# and Visual Studio when I used it 20 years ago. Boo was much easier to get started with back then, when you just wanted to try out .NET 2.0. It took me a few minutes to download and install .NET Framework (~20 MB) and SharpDevelop (~15 MB) versus five CDs of Visual Studio 2002 which took an hour or so to install on the machines of that time. And yes, I already skipped the installation of the Microsoft Developer Network (MSDN) documentation which as far as I remember already took an hour alone.
For some reason the installation of a development environment for Java was also much easier than Visual Studio, i.e. one had to download Java Runtime Environment (~100 MB) and unpack it, and then download Eclipse IDE (~100 MB) and unpack it. When you downloaded both archive files already it took a few seconds to unpack it and double-click on the eclipse.exe.