Before nginx was a thing, I worked with a guy who forked apache httpd and wrote this blog in C, like, literally embedded html and css inside the server, so when he made a tpyo or was adding another post he had to recompile the source code. The performance was out of this world.

Fantastic way to start a shitstorm. You people don't even use search function logged out, because if you did, you would know they changed it in 2016. Microsoft has nothing to do with it.

https://news.ycombinator.com/item?id=11321623

:00 - :ff

Edit: Just learnt this can be also noted as:

:: - ::f

Old issue, so why post it now make it sound like MS demands something?

Opened 11 months ago Last modified 11 months ago

It's a regression, so ffmpeg should fix a regression.

You live like this?

All (doesn't seem like MsSQL supports it, I thought that's a pretty basic feature) databases have special configuration that warn or throw error when you try to UPDATE or DELETE without WHERE. Use it.

Blog content was stored in memory and it was served with zero-copy to the socket, so yea, it's way faster. It was before times of php-fpm and opcache that we're using now. Back then things were deployed and communicated using tcp sockets (tcp to rails, django or php) or reading from a disk, when the best HDDs were 5600rpm, but rare to find on shared hosting.

It doesn't make the content in any way out of date

And because Microsoft moved their HQ to Munich

Because it's free and reliable

No, it won't.

Serialisation, marshalling issues and mental overhead of using compareTo

(C++)++

https://dtinth.github.io/comic-mono-font/

You probably want this now https://marketplace.visualstudio.com/items?itemName=humao.rest-client

You're telling me about compiling JS, to my story that is so old... I had to check. and yes, JS existed back then. HTTP2? Wasn't even planned. This was still when IRC communities weren't sure if LAMP is Perl or PHP because both were equally popular ;)

After doing it for 15 years, I must be good at it and everything should be easy.

hidethepainharold.jpg

I’ve thought of doing pen testing (later on in my career), but I’ve come to realize that it is better if users just started using privacy-respecting FOSS software like Signal, because if you give a hacker enough time, patience, and the right resources, they could hack into anything.

Your idea of pentesting is so far from what it looks like in reality that it's probably not a path for you, at least not now. Let me explain: how am I going to protect my banking app using Signal? How will I know if our JSON unmarshalling library used by transaction service isn't vulnerable or exploitable? What FOSS software shows me live dashboards of deployed software in container and their security risk?

everybody still needs them and they’re not going away any time soon.

Bank is a civilization old concept, it has always been here and will be. Banks are so durable, they will run after our civilization ends.

It's supported in MySQL and MariaDB out of box:

https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html#option_mysql_safe-updates

In Postgres there is an extension for it:

https://supabase.com/docs/guides/database/extensions/pg-safeupdate

Seems like you have some organizational and technical debt in the company that would be worth addressing before agreeing to be on-call

Noticed that Hibernate session (DB ORM session) was leaking to Jackson (JSON marshalling), potentially causing infinite n+1 problem. Changing a few lines of code to lazy loading and fixing the session leak reduced our daily data transfer from DB from 5.6Gb to 170Mb.

Not sure if this was the biggest optimisation, but definitely the dumbest issue.

you are supposed to have written the tests and to have written your code with pair programming,

I commented out the tests because they were failing, pipelines were green so I merged. Now it's running on prod. What do you do?

What were the architectural decisions you made?

Learning from a documentation. Got a book, went offline and finished the book and training exercises without looking for anything online.

I sell on eBay for the price of postage

agile happend

Being offline doesn't mean not using a computer. I still had IDE and https://devdocs.io/ for better ctrl+f experience.

On BSDs you can do ctrl+T and it prints progress, there were plants to implemented this on Linux, but it didn't get enough traction.

Not banking but transfer proxy space.

Why would you need multiple distros at the same time?

Most likely debian or debian-distroless

Even for an outage starting at 2am lasting 6 hours?

Just not in Java…

I think you're biased against Java. Amazon was started in C/C++ and Java J2EE during times when to configure a webserver required writing like 300 lines of XML just to handle cookies, browser cache and a login page. Until recently BMW had their own JRE implementation. It's not a secret that simcards, including these in Tesla cars run JavaCard too, even government issues sim cards in EU have to run Java Card, not C++. Everything was always fine with Java until ECMA Script appeared and made people iterate on software versions faster. New programming languages and team organisation methodologies left some programming languages in the dark, but this included C# too. All are quickly catching up. If Java was so bad, it wouldn't be here with us today, like Perl.

The one you know best

It compiles = it goes to prod!

We had developers leave my company because they had to work with scala during 2 -> 3 migration. Everybody hates it now

You're all gonna have to learn to die together

There are two schools:

1. the best stack is the one you know best
2. the best stack is the one designed for the job

Remember that Google was written in Python and Java. Facebook in PHP. iOS in Objective-C. GitHub in Ruby on Rails.

JavaScript bad.

They do say that, but how much can it be trusted? Can they really detect all native interface calls? Be aware of all future file system checks or event driven programming paradigms? hashset.getOrElse() where uniqueness decides future flow? I'm sure we will be experiencing or at least seeing bug reports related to predictive debugger triggering mutations.