flanfly

A neat trick I was told is to always have ballast files on your systems. Just a few GiB of zeros that you can delete in cases like this. This won't fix the problem, but will buy you time and free space for stuff like lock files so you can get a working system.

Good showcase. Your code will match the first parameter that has <param> as a suffix, no necessarily <param> exactly (username=blag&name=blub will return blag). It also doesn't handle any percent encoding.

Props to Intel duping AMD to buy Xillix for whooping $50B

I'm German and had a startup in Germany (standard UG holding + GmbH).

My one advice to anyone thinking of starting a company is: don't do it in Germany. Tax burden, insane bureaucracy and a conservative, tech adverse local market put you at a disadvantage against UK/US peers.

>German founders are incentivized to move abroad before exits

Don't do that. The tax office will treat that as a sale and will tax the current valuation at 20%.

As a long time vim users, elisp is something I always envied the emacs guys for. I love vim and bram but viml is a pos. The result were a multitude of language bindings. Of course, now everyone uses their favorite language to write extension which meant that most non trivial vim configs require a working python, perl, ruby and ocaml interpreter on the system. Lua in nvim fixes that, now I only need to install a billion language servers before I can start working :D

I quoted this, in full, in my MSc thesis. It's both a light hearted introduction to the Halting Problem and something you need to reference quite often when writing about static program analysis. Good times.

Funny and a good reminder that there is much money to be made from just packaging code off Github in a usable UI and providing binaries for the 99%.

It has a lot to do with Google. MS Research it a pretty good example how to turn your industrial research into products.

Finally a reason to update from 4.2.0

Good news for cryptographers in case we need an alternative to LWE and coding-based PQC.

It's an integral part of my workflow now. I love it. My common use cases are

- generating doc comments that are 99% correct

- completing boilerplate like error handling (f- you golang)

- write a "quick start" skeleton for unknown libraries and frameworks

I got these on Brave on two different computers. Disabling hardware acceleration fixed it. Both had Intel graphics.