nox100
Joined 2 years ago
Joined 2 years ago
Worst luggage I ever owned was Rimowa. It was the most expensive I've bought and broke several times. They'd fix it, but who wants to spend their vacation taking their luggage to the repair shop (and lugging it full from the airport to the hotel while it's broke)
Worst and most expensive jacket I ever bought, Paul Smith, got a hole in the main pocket within 30 days and the hanging hook in the collar broke in 2 weeks.
Worst jeans I ever bought, Diesel. Ripped in 1 month.
Moving overseas I had to buy a new sofa in 2021. Middle of COVID, Ikea didn't have any I couldn't wait. The sofa I ended up with is the cheapest shit sofa I've ever owned. The materials are clearly inferior. No part of it is cleanable. The cushions are one sided so can not flip them in 4 directions, they only fit one way. I got tired of looking and settled on these though, expecting to replace them.
Anyway, my point was (a) I understand your POV but also (b) there are possibly some good under $1000 sofas. I've had similar luck with a few Ikea dining room tables that were solid wood, not particle board.
VS Today wheer there are 1000s of websites that will teach you JavaScript and 1000s of free video classes and hundreds of thousands of free examples. JavaScript is several orders of magnitude more discovable than basic ever was
I get why it's that way, backward compatibility. The problem is, the original way, the path of least resistance, is now effectively deprecated, but it's the official syntax.
char* s = malloc(size);
is considered bad code. I get why. But, in a "good language" the default would do the right thing and I'd only escape into bad code by extra work so that all the easiest code to write did the right thing by default.C++ is trying to fix all that old bad code by coding standards and linters but I don't want to have to type a bunch of boilerplate I need to memorize to do the right thing. I want the right thing to be the most obvious, no brain cells required path.
JavaScript is way more powerful than Basic on any of those 4 platforms. The canvas 2D API is way more capable and easy than what came with those systems. Even getting something like
<input type="text">
Was 50-150 lines of code in BASIC, by which I mean a text input line with a cursor and editing and not just BASIC's "INPUT" command which provided nearly zero editing support.Libraries like pixi.js or three.js or p5.js etc make it trivial to get fancy graphics on the screen. Making something you can share it with your friends or the entire world with a link, even if they don't own the same type of machine running the same OS. Host them on codepen, jsfiddle, github pages, all free.
I loved my experience with Basic and those old machines but I wouldn't force my kids to learn that way.
> Instead of sending streams of bytes to render text, it sends streams of encoded X Windows commands to draw the UI.
(Simplified) VSCode is sending no bytes to a server when you're editing a file. The entire file exists on the client, you can edit all you want and everything stays on the client. Only when you pick "save" is a data sent to the server.
My understanding with X Windows is as you mentioned above, you press a key, that key it sent app on another machine, that other machine sends back rendering commands. Correct? Vs VSCode, you press a key, nothing is sent remotely
Note: There's more to VSCode, while it doesn't have to send keystrokes and it is effectively editing the file locally (so fast). It does send changes asynchronously to the remote machine to run things like the Language Server Protocol stuff and asychronously sending the results back. But, you don't have to wait for that info to continue to edit.