Bun is a Node.js/Deno alternative. I.e. it's made to run JavaScript code *on the server*.

Naïve question: why didn't they choose to fly slower instead, and save fuel?

Is it impossible to do so? Or not cost-effective?

You need to get out of your cave. Kotlin is now the primary language that Google advises to use to develop Android apps (you've heard of Android, right?), and it's becoming strong on the server-side as well, where Spring (the most used server-side framework on the JVM, which is itself the most used programming platform), among others pushes its use too.

If the speakers are business executives and the target audience is CNN journalists, it's not a tech conference. It's a business/media/marketing conference.

Techies speak at actual tech conferences. And I usually enjoy and learn quite a few things in the tech conferences I attend to.

No, you don't. But, you allow a hacker to modify the persisted bytes and thus make the production code load objects that have a state that they should never, ever have, breaking their invariants, and possibly make them call constructors of classes that they should never call.

From my experience of answering tons of questions on StackOverflow, a huge deal of newbies or self-taught programmers program the following way:

  - try some random thing
  - get an error
  - ask how to fix the code (and not even post the error)

You should teach them the right process, which is based on reading (a lot), experimenting, analysing errors, making deductions on what needs to be changed, and repeating the cycle:

  - read documentation, before starting programming. You need to understand the big picture and the fundamental concepts before using some technology. You need to know what's in there, otherwise you'll reinvent the wheel or follow the wrong direction. This can take hours, or even days, but will save a much bigger amount of time later.
  - don't try random things (like guessing method names, guessing what arguments to pass, etc.). Read the API documentation.
  - Experiment, compile and test what you did very often. Don't write 500 lines of code before even compiling them. When you have an error, read it, carefully, using your brain. Try making sense of the words in the error. Don't guess. Don't try another random thing to fix the error. Read the documentation again. Make deductions based on observations.
  - Format the code religiously, and comment it, while writing it. Reading your own code is what you make the most when programming. If it doesn't have the right structure, you cannot reason about it. If it doesn't have comments, you'll forget what a method does or what arguments represents immediately, lose time rediscovering it, and take bad decisions based on poor understanding of your own code. Commenting code also makes you realize design mistakes
  - Use good names. Forget about single-letter variables. Programming is not math. If something is a save button, name it saveButton (or save_button, depending in the standard naming conventions). Not s. Not sb. Again, you'll read the code a lot, and good names is what makes it bearable.

All of this is based on a quite simple competence: reading. Unfortunately, many would-be programmers don't know how to do that.

Err, TypeScript is a compiler. It compiles to JavaScript. JavaScript runs in every browser.

No, because that would mean the password is stored in clear text in the database, or hashed but not salted randomly, which would be a much bigger security problem.

To securely verify credentials, you get the random salt and hashed password of the user, thanks to the provided login, in the database. Then you salt the password and hash it, and compare the result with the password you got in the database.

French schools already have the solution for this problem: toilets are so disgusting that a lot of students avoid going to the toilets, even just for doing... what you're supposed to do in toilets. Sad reality.

If only the keyboard had a proper apostrophe character!

So, if I want to share a 1 GB file with 3 friends, I need to upload it 3 times? And send 3 different (non-encrypted) emails?

Or I could just use GDrive or Dropbox, which don't have this awful limitation. Seems to me that they forgot usability an only thought about privacy and security.

Week after week, Uber shows that it doesn't give a shit about the law, whatever the country is.

Week after week, Uber shows that it doesn't give a shit about its employees (or, as they claim, their independant drivers).

Why would Uber management give a shit about this poor woman? Why do people accept to work for Uber, given the constant reminders that Uber doesn't respect any rule, nor anyone?

Did it really have a white background?

I don't see any background color specified in the markup, and I'm not even sure it was possible to do that at that time.

The first web page I saw, in one of Netscape's first version, was later, but I remember that Netscape found it cool to have a grayish background back then rather than a white one. I think Mosaic had a gray background too. What was the browser used to display that first web page? How did it look like?

I certainly write some JavaScript. But it doesn't mean I like it, or even that I chose to. I just don't have the choice. Sure, I can (and do) use TypeScript or CoffeeScript, but they all suck and I would choose any type-safe language over them if I could. JavaScript is unfortunately the only language that the browsers support. I really hope that WebAssembly becomes a real, usable thing soon, and that better type-safe languages for the browser emerge. Or even better: that existing languages, like Kotlin, start targetting it and that a saner ecosystem emerges around it. I'm sick of JavaScript, and even more of its awful ecosystem (NPM, etc.)

I take the train every day to go to the office, and people often sleep in it. What you describe never happens. the vast majority of people are honest and don't steal from other people. Especially the kind of persons that takes the train at 7:30 in the morning. And even if a thief wanted to steal someone's shoes, many other honest people are in the train watching and prevent the thief from even trying. The train is way better than a car: it goes faster; I can read, sleep, or work; I have a power outlet for my laptop; the journey is much less painful for my back; there is no traffic jam, and it's way cheaper than the car.