Kissaki
They're not demanding anything. They're describing how the current meaning of REST is nothing like the original one.
They're making a point for not splitting application state and logic into client and server with shared knowledge. If you're making that a pretext of course their argumentation won't fit. They're describing an alternative architecture and approach. Not an alternative protocol for the current common web application architectures.
Presentation/Lecture; bad software quality due to software stack complexity with increased separation of layers and participants
SoC (System on a Chip) hardware for embedded/smaller use cases is very common and successful.
Suggests "Direct Coding" with direct hardware access as a possible alternative approach to PC hardware interfacing. Implementing that is more about commitment than difficulty. Depends more on hardware producers than software developers. A lack of drivers could give a fairer playing field between manufacturers.
German pro basketball team relegated to lower division due to Windows update
lol
Seems like a Ruby issue and suggested improvement? Using keyword arguments does feel like introducing a type of typing.
In C# I use records for simple, naturally behaving types, I can define explicit and implicit cast operators, so I have to choice between requiring explicit casts or not (because they make sense to require or are not necessary). I can use var to define a variable without specifying a type, and it is deducted from what it gets assigned - but is still that specific type and gives me type safety.
In Rust, as far as I understand anyway, traits define shared behavior. In Go interface implementations are implicit rather than explicit. With these, there's even less of a need of elaborate explicit typing like the post argues/gives an example of.
In general, I've never had considerable effort or annoyance implementing or using typing. And I know what it's good for; explicitness, and in consequence, predictability, certainty, increased maintainability, and reduced issues and confusions. If following references or refactoring becomes unpredictable or high effort, it'd be quite annoying.
When I'm coding JavaScript adding JSDoc so the typing information gets passed along is quite cumbersome. Without it, the IDE does not give intellisense/auto-completion or argument type matching. JavaScript is better with it, I consider it worth it with IDE support, but it is quite cumbersome. (I try to evade TypeScript compiler/tooling overhead.)
A programming language can offer extensive auto-deduction while using strong typing. With appropriate conversions in place, it will only report conflicts and where it was intended to.
I'm thinking of where I enjoyed dynamic natures, which I certainly have. But I don't think that's a matter of typing. It's a matter of programming language interfacing to typing. If in PHP or JS I make a change, hit F5, and get an error, that's not any better than the IDE already showing it beforehand. And for the most part, I can program the same way with or without typing.
Man, this became a long text.
I'm just glad we didn't end up with this one (seen in the ticket)
Damn, sad story behind the color
The field is incredibly broad. Choose a field or employer or project that's not doing that an you're fine.
Are you sure? I'm not very active in that ecosystem, but if that was prevalent in the past, surely there's still tutorials and stuff out there that people would follow and create such projects even today?
More than that, it seems to me that the official python docs for packaging [still] talks about setup.py. Why would people not use that?
got it; arse
It would certainly be an issue if you didn't have one
lol; committee with consensus by violence?