HN user

2716057

203 karma
Posts1
Comments25
View on HN

I would not worry too much about the maintainer - judging by his GitHub profile he does a bit of professoring as a side hustle ;)

Thank you Christian Clason for giving us nvim-treesitter! And always remember, for each idiot insulting you there are thousands of happy, silent users.

As long as there are consumers paying for hardware ownership there will be businesses willing to sell it to them. The worst scenario I could imagine is that one has to pay a premium for fully-owned hardware simply because consumer's desire for it becomes an oddity and it is thus sold in low quantities.

The current AI-induced shortages aside, the times have never been better in my opinion. There is overwhelming choice; ordinary consumers can access anything from Raspberry PIs all the way up to enterprise servers and AI accelerators. The situation was very different in the 1990s when I built my first PC.

Nice work, could be useful to beginners!

Consider handling extreme cases gracefully with a "it is not recommended to go running/cycling outside in these conditions". Otherwise I get

It will be -37°C, clear, windy so you should wear:

Hat

Long sleeves

Jacket

Gloves

Leggings

brrrrr....

Place modifiers on the thumb keys or - if you don't have any of those - use home row mods!

My ranking of measures from most effective to least effective:

1) Do everything you can to minimize workload of weak fingers (pinky & ring fingers). Just flipping control and caps lock is often not enough.

2) Split keyboard; halves roughly shoulder-width apart. Optimize for straight wrists both at rest and "in action". This usually results in zero tilting or slightly negative tilting.

3) Concave designs.

4) Tenting.

Anecdotally I agree with the message, but the research looks weak indeed.

A simple snapshot assessment and some scoring of an individual's (entire, self-reported!) social life is too simplistic. The measurements would have to be performed throughout the life of each participant with sufficiently high frequency.

The workarounds on this page mostly suggest to use large public resolvers. Feature request (not sure if the author is on HN): it would be interesting to know which domains are blocked by 9.9.9.9, 1.1.1.1, and especially the new DNS4EU service.

Depending on your network configuration I could imagine abuse of EDNS(0). This is used for example by NextDNS to identify which device (MAC) on your local network sent the request in order to apply specific filters and log the request. A not-so-friendly DNS could sell such information.

After a recent sports injury I got my hands on a muscle stimulation device (Compex). What I learned:

1) These devices do not only massage. Depending on the settings they can force incredibly powerful contractions with muscle ache the next day. This feels like a real workout.

2) Because you do not have to think about the movement it is relatively well-suited to desk work. I can easily code during the sessions (which usually take 30-50 minutes).

3) Downside is that attaching the electrodes can take 5-10 minutes.

I came to like it and will continue using it after recovery - while working!

Of course this is no substitute for actual exercise with voluntary movements.Get up, do some push-ups, pull-ups and throw in squat jumps or similar high intensity stuff to get the heart pumping!

German here. I would be very interested in the government agency you are alluding to.

There are laws regulating layoffs due to operating conditions (Kuendigungsschutzgesetz). But these laws do not allow the government to intervene directly in company affairs - that would be communism! If a company wants to restructure "for internal reasons" (rationalizations are specifically mentioned) it is allowed to do so. This includes offshoring, moving workload to contractors, or simply getting rid of a department.

However: many of the large companies (eg. SAP, BASF, carmakers,...) have collective labor agreements. These agreements often exclude layoffs due to operational conditions within a certain period. Under very special circumstances layoffs are still possible in such arrangements, but the companies have to prove their economic hardship and the layoffs often end with a sort of golden handshake. If they happen at all :)

One can tamper with the data or the power meter itself. If a cheater is faster than a competitor pushing more watts, his team will respond with the usual BS: the bike's aerodynamics, stiffness and its super-innovative tires made him faster...

However, mandatory power recording could become quite valuable over the long run. The peloton should be large enough to allow data scientists to detect the abnormalities (unless all the teams reach an agreement to cheat consistently ;)). Once a history is built over a decade or longer, "unphysiological" power output could be detected quite easily.

Florian Scheck's textbooks in the Springer Graduate Texts in Physics series could also serve as a bridge. Though very challenging for the non-mathematician I've grown quite fond of "Mechanics: From Newton's laws to Deterministic Chaos" and plan to read the other Scheck books in the series as well.

Especially true if that child or its mother has a huge market capitalization, large profit margins, highly-paid employees and shareholders eager to reap some more $$.

If the public starts to see LLMs as highly sophisticated copyright laundromats it would most likely hamper further investment & development in that field.

No, no, it's all wrong.

Here's how we digitize our administration in Germany the proper, Germanic way:

A fixed sum for digitization is allocated and the local government publicly advertises a project. A bureaucrat higher up the foodchain has a friend/cousin/former colleague who runs an IT service business side gig. Guess who will win the contract. The friend/cousin/former colleague starts building by outsourcing the project to some sweatshop. The project will exceed its initially planned costs and timeline by a factor of two or more. Once completed, the final product will consist of a clunky frontend allowing the user to fill a form. After the user has completed the form, it will be distributed via e-mail to the low-level clerks. They will print it out and process it by typing the very same information into another software running on their work computers. Print again. Then the user has to schedule an appointment at the local administrative office to get the form signed and stamped in person. Upon completion, the finalized form will be faxed to the next administrative authority in the chain.

The frontend runs on a Raspberry Pi located somewhere in the administrative building. That server will of course be turned off when all administrators have left the building (save energy!), meaning the frontend will only be available during weekdays from 8 am to 1 pm.