tsujp

Could you please elaborate, ideally in as much detail as you're comfortable sharing, on your Emacs and adjacent (org-mode, magit, any kind of syncing to your mobile phone with org-mode if that's done) workflow please. Often I find seeing people's real workflows (in detail and not wishy-washy) to be helpful since it gives me a concrete nucleus to crystallise off of... so to speak.

JS also has Crypto.getRandomValues()

The problem with the PGTK frontend is it is notoriously EXTREMELY slow. The latency on user input compared to the X11 (especially Lucid) version has some people reverting back to X11/Lucid.

When I do run Linux I run Wayland, I daily drive macOS, but better than both are what you already allude to: the Emacs widget toolkit which will focus on replacing the GUI frontend with SDL and also (equally potentially) introducing an actor-type framework (akin to BEAM's) for communication to decouple that GUI.

See: https://news.ycombinator.com/item?id=41821494

Understood, but in this (hypothetical) example his mother probably doesn't know exactly what angular velocity or torque are, so making things even simpler with a laymans "power" serves to get the point across.

One could include torque in the explanation to which the follow-up is probably "what's torque?".

The simpler one goes for that initial understanding, in most cases, the less technically correct one is; by design that helps the newbie learn and build up to a more technically correct understanding later on.

In general relying on excessive detail or jargon is symptomatic of not really understanding something when required to explain things in simple terms. I believe Richard Feynman said as much.

The general idea is people hide behind that detail/jargon precisely because they don't REALLY understand it enough to explain in simple terms what it is. That doesn't mean everything IS simple of course.

I assume you know now but in simple terms: the clutch connects the engine to the gearbox (transmission), so how well the clutch is engaged (connected) helps control speed. Gears multiply (increase or decrease) power from the engine depending on the gear you've selected.

I'll need to look into this but if anyone knows: is this available (easily) as a standalone package somewhere; think using the engine from a CLI without needing or contacting Google Sheets at all.

FINALLY!!

For 12 years visually vertically centreing text has required adding a padding or margin of a few pixels to the bottom or top, now (when adopted) it can be done properly.

Hey Jarred, big fan of your work on Bun.

Until recently I've been using Deno (mostly to avoid using Node and the tooling hell that entails) and it looks like for my use-cases Bun is getting there. I've had a pleasant experience using Bun as the basis of a test harness.

Here's my question (with a tiny bit of lead-in):

What I like about Deno is the integrated LSP (reducing tooling hell), are there any plans for Bun to feature this too? Bun already internally transpiles TypeScript which is great but having the LSP bundled too would give this single binary integrated experience a boon I feel.

Looking forward to Bun 1.0!

P.S. I'm starting to stretch my Zig muscles, you looking for Zig developers? ;)

Fines should be at least 100% of _revenue_ from these activities to actually punish the business. At the very least 100% of _profit_ from the activity. Anything less is cost of doing business since it's by definition a net profit.

This is the most disgusting thing I have ever read. My blood is boiling to the point where I genuinely don't see a bright future.

Ben Wiser (Google), Borbala Benko (Google), Philipp Pfeiffenberger (Google), and Sergey Kataev (Google) have got to be the most repugnant people on the planet for pretending this is anything but a scheme to destroy all privacy and freedom on the web all so fucking Google can sell more ads.

Location: Melbourne, Australia.

Remote: Yes, hybrid is also fine.

Willing to relocate: Yes: U.K (I'm a citizen), South Korea, Japan, Germany, Singapore, France, The Netherlands, U.S., or within Australia if it makes sense.

Technologies: {Java,Type}Script, Ruby (on Rails), Node/Deno, React, SolidJS, AWS, Azure, .NET, C#, F#, some C and Zig, POSIX Shell/Bash, some Python, Terraform, Ansible, SaltStack.

Résumé/CV: https://www.linkedin.com/in/tsujp/ (email for full PDF, references) and https://github.com/tsujp

Email: jc [plus] j [dot] yc [at] wz [dot] ht

I do DevOps and Software Engineering (particularly full-stack web but increasingly more systems programming). I will happily learn new technologies and enjoy learning in general as well as partaking in challenging environments where application of knowledge and skills solves problems.

The changes should be the main meat of most commit messages and if the intent or other options considered add value to that then they should be included below.

The reality is if the intent, other options, relevant notes etc are not valuable then they will be lost to time (no loss). If they are valuable where else are you going to put them? Some wiki or knowledge store for your project? How will you know that this specific commit and that (probably) sparse text in said knowledge store are related? Why not just put them together where they belong anyway.

Commit messages are not valuable when they are maximally short. They are valuable when they describe the changes the commit applies and ANY other relevant information for people (including the author(s)) in the future so that said people can understand the commits effect and other relevant information.

For an example of amazing commit messages look at PostgreSQL’s. They are sometimes long with the changes, notes, intent etc and sometimes short.

There's also Boon which I like quite a lot but I opted against using mostly because of all the places I would need to type where I wouldn't have access to Boon unless I ported it (a plan I assure you but one lumped behind 1,000 other projects TODO).

https://github.com/jyp/boon

Addressing just the capture: I don't see the problem with `||` at all, in-fact I think it's elegant. I do like (most of) Ruby's syntax so that's probably where my fondness of this comes from but I am not a veteran or seasoned Ruby expert by any means.

Some prior threads:

- https://news.ycombinator.com/item?id=28850861

- https://news.ycombinator.com/item?id=28255116

- https://news.ycombinator.com/item?id=23164614

I don't know how I feel about this.

It is _technically_ cool but I feel like this existing is a definite step backwards with regards to Node.js' lack of modern web APIs.

Software like this relieves pressure in moving from Node.js specific APIs towards standardised web APIs and in addition to that itself boasts about portability by ignoring modern features too. From their WebContainer vs Nodebox FAQ:

    Nodebox runs on any browser because it was built from the ground up with cross-browser support in mind, avoiding modern features like SharedArrayBuffer."

Link: https://sandpack.codesandbox.io/docs/resources/faq#how-does-...

So now we've got an escape hatch for Node.js not having to implement modern APIs because software like this implements its runtime for the browser, and also this same software removes pressure on browser vendors bringing their implementations up to webstandard specifications by "... avoiding modern features".

While this is _technically_ cool I feel like it's a lose-lose for the overall ecosystem.

All specifications (with links to repos): https://solid.github.io/specification/

Solid protocol specification repo: https://github.com/solid/specification

Honestly I hope Google go through with this as it will direct people to Firefox so they can continue using ad-blockers like uBlock Origin.

I don't know how many will come but if Google wants to implode their plugin ecosystem in favour of more advertising, and if that action increases Firefox adoption (and thus a healthy browser ecosystem via competition) then I am for it.

I haven’t used Heroku in a few years mostly because I haven’t had the need but also because it feels too expensive.

The 30 minute sleep is way too high and as others have mentioned will easily drain half your hours away. If you could configure it between say 10 and 30 minutes (I’d say as low as 5 but this is the Hobby tier) that’d feel a bit fairer.

For those not aware this is about 35% of the population of Australia which is around 26 million.

You can still use the old Reddit UI by the way. If you use an account configure it in your account settings otherwise make sure you visit `old.reddit.com` e.g. `old.reddit.com/r/news`.

The day `old.reddit.com` stops working (and the API prevents a remake) is the day I stop using Reddit.

This is categorically incorrect. You can have any amount of ETH (up to 32 because there's no value in going higher) and be a validator participant if you partake in a pool.

Hacktoberfest is about contributing to open source yet the community is on Discord...? I guess IRC and Matrix aren't viable mediums to strategise README.md contributions?

I genuinely cannot reconcile the irony here, _maybe_ "because it's easy" which would fit in line with spamming README.md edits for participation.

Honestly... good. For company-private communication sure but for FLOSS projects it genuinely irks me that Slack (Discord too) is _ever_ used as a communication medium. Make a forum, use IRC/Matrix or even Gitter/RocketChat.

Almost all the time whenever I reluctantly decide to join a FLOSS project's Slack it works out like this:

(1) Hunt for the invitation link and hope I can actually join because a lot of them have that annoying error where if your email doesn't end in `@theirproduct.com` you cannot join. Unless I really, really, REALLY want to join I give up here 99% of the time. (2) If the invite link hasn't expired, and if they allow any email to join then I am in but the channels are all basically ghost towns even for big projects like Kubernetes.

I suspect the friction in being able to easy join versus just visiting a website (forum) or opening a chat (IRC/Matrix, even Gitter) is why.

    there's just a small number of validators, which is just going to be the ethereum foundation and friends.

There are over 415 000 validators.

See: https://beaconcha.in/

While obviously extremely impressed with Bun and Jarred's achievement (especially because I really like Zig being similar to C) I'm also shocked that he was able to get a 3-letter `.sh` domain (bun) _and_ a 4-letter `.sh` domain (oven) both real words!

Looked to me that Oven was registered shortly after Bun exploded in popularity.

I can't wait to see the corpse of Tolkein's IP bastardised by more "modern" content.

I miss being 10 and watching LoTR for the first time, I genuinely don't think I could work up the interest to watch another piece of entertainment released after the disappointment and insanely high levels of bloom-filter in The Hobbit. Amazon's upcoming show does away with the Elvish languages, and the established appearance of the universe.

I really like this. I like that it's bluetooth _optional_ with multiple devices remembered, USB-C, has a command key and control key _separated_ (I'm well aware you can do this in firmware for other keyboards that support it), the much lower profile, and the typography.

I've gone through a few different mechanical keyboards including things from Ramaworks and every time I get fed up with the bulk, the tedium of lubing switches, finding good key caps _with_ the legends I want, and then trying to get things as quiet as possible without super mushy key presses. If this can solve that I will buy one instantly; and I've signed up for the waitlist.

These specific microVMs are managed by: https://github.com/containers/libkrun#goals-and-non-goals (linked directly to project scopes).

In summary though (others redacted):

    # Goals
      - Be compatible with a reasonable amount of workloads.

    # Non-goals
      - Be compatible with all kinds of workloads.