Comments by "Vitaly L" (@vitalyl1327) on "Continuous Delivery"
channel.
-
1
-
oh, really? Any developer must master dozens of languages. Any capable developer must continuously create new small languages, because Language-Oriented Programming is by far the most powerful abstraction tool. A developer with only one language under their belt, especially such a crippled and ill-designed language as JS, is not a real developer.
Want to be "full stack"? Master the entire stack underneath your level of abstraction. Starting with analog and digital electronics, HDLs, all the necessary elements of computer architecture, all the PLT-related mathematics, PLT itself, a deep understanding of compilation and interpretation methods available, a deep understanding of how operating systems work (and when and where to use them or ditch them altogether). Understand networking, from PHY levels to high level protocols, and know where you should be on this stack of abstractions depending on your goals. There's a lot of critically important knowledge there. Javascript, browsers and all that meh are not among even the tangentially impactful pieces of knowledge.
1
-
1
-
1
-
1
-
1
-
@ApprendreSansNecessite for me, it sounds like a weird design, when similar data processing happens in different parts of the system. For data model - yes, it can be the same while flowing through the system, but it does not mandate the same language that handles the data in any way. Validation is normally just a part of the data model.
And things like data model, validation, etc., should be defined in a higher level (ideally, declarative) language anyway, and then translated into whatever language whatever part of the system is using. You're likely familiar with rudimentary forms of this approach employed in IDL and similar protocol / data model description languages. There's often dozens of languages involved, with a single data model in between them.
I admit I stay away from anything related to web, so may be unaware of some of the rationalisation behind common design choices in that world. From far away, the whole web stack looks like it's massively overengineered and badly designed on all levels though.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
@skyhappy first, let me reassure you, that you have no faintest understanding of the real world. It's pathetic, frankly, how code monkeys always run around rambling about the "real world", why they don't even possess a mental capacity to even start understanding it.
Secondly, no, computer science is the most important science out there, binding all the other sciences together. It's the science of what computation is, and our universe is built on the notion of computation on many levels. You won't understand it, of course, I'm saying it here not for your benefit. I'm a nuclear physicist who had to turn to computer science, because there were no answers to my questions anywhere else. And only computer science could finally make all the pieces of the puzzle click in.
And computer scientists are supposed to explore this branch of knowledge. Not write some pathetic crappy code, like your kind does.
And I'm so glad I'll never have to work with primitive nobodies with overblown ego like you. That's another great feature of the current market, it's very picky, and it works exactly as intended, leaving your kind out of anything meaningful.
1
-
1
-
1
-
1
-
1
-
1
-
@vincentvogelaar6015 apparently you do not understand how to use LLMs. They're not any different from our own minds - we cannot reason either, unless we use tools, such as formal logic. So give LLMs their tools - give them an ability to write down reasoning step by step, to verify the reasoning using formal methods (as in - make them write down the steps as HoL proofs or Prolog predicates). Give them a sandbox to debug the proofs, just like you do with any other code. Provide a critical loop to make sure they did not miss anything from the formulation of the problem when translating it to a proof.
I'm using LLMs for solving engineering problems, and reasoning is a crucial part of it. Even very small models (like Phi-3) are perfectly capable of reasoning on a level beyond the capacity of an average engineer, when given the right tools and proper sandbox to test the ideas in (akin to our imagination).
Also, LLMs perform the best when reasoning about things that were not in the training set. E.g., they write much better code in languages they've never seen - because they're forced to do it slowly, verifying every step, instead of churning out answers instinctively.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
Many languages, some are good, some are mediocre, but none as awful as JS. I use C, C++, various flavours of Lisp (including Scheme), Tcl, Verilog, ocaml, and a few more, including even Fortran. Nothing is as ill designed as JS.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
@awmy3109 right, what a great argument! Since only JS is available in a web browser, JS is somehow now a great and performant language.
Simply for a virtue of monopoly. Nice.
But this is not what OP was talking about. This is how people with experience from outside of web see the web ghetto. Any time we take a closer look we recoil in disgust. This whole web thing is a pile upon piles of utter crap, and it should have never been like this.
Also, people like you are very often guilty of not even trying to think if they really need to build a "web app". Turns out, very often they should not, but they still do, because this is all they know. A lot of time a native application is a far better solution. Even more often, no UI at all is even better, yet, the people with such a severe professional deformation fail to see it.
Now, you claimed JS is somehow performant (we know it's not, not even close). You claimed you don't pay for abstractions in such a language. Wrong again, you pay dearly. Admit you're wrong and stop moving the goal posts.
1