skysight-inc/HackerNews huggingface dataset:
I used to be a huge i3 user (and sometimes I give in to the temptation to load it up and mess with my config). I love tweaking my desktop to make it look like it should be on /r/unixporn. However, there are certain desktop things I don't enjoy messing with at all:

- audio

- displays

- bluetooth

Audio is especially confusing on Linux because there are so many parts to one system. Even after researching PulseAudio, ALSA, Pipewire, Jack, etc. it is super hard for me to know exactly what does what on my Linux machines.

I found that with i3 I often spent more time tweaking my desktop than actually doing work. However, I think that tweaking like this is actually super fun and educational on how Linux display stuff works -- I would never discourage someone from taking the time to mess around with i3, bspwm, or an alternative.

My perfect balance is GNOME plus the Pop! OS shell extension[1]. I'm not a Pop! OS user (and likely never will be) but I loooove having tiling in GNOME and being able to have all the stuff I don't like to manage just work.

[1] https://github.com/pop-os/shell

EDIT: minor grammar tweak
There’s the concept of Zones and you can measure the intensity directly with a power meter or indirectly with HR.
Anything that reaches close to your sustained max HR or max power is considered high intensity as it uses different energy systems to produce muscle energy
And yes there’s overwhelming research that for a non pro athlete you should only do one or two high intensity workouts per week (and pad with low intensity sessions to get enough training time)
In my experience they are correct all of the time for simple renames. It's when you move a file and make substantial edits that it gets confused.

I think it's reasonable to argue that git shouldn't get confused in this scenario, but you could also do your renames in one commit and your changes in another.
I personally believe that making diffs more human friendly is the next step of evolution we need. I work with a team on a NodeJS+React project and nearly every other PR shows up as "Something changed in package.json, something changed in package-lock.json, some static assets added/modified, some JSON changed" etc and it makes reviewing code quite unwieldy (esp. since it forces folks to use Github UI interface to even see blob diffs. which is quite opinionated on when it collapses a file in the PR, and how it determines what changed in a file). I feel like git was perfect when "code" was nearly almost completely text and patches were sent over email, but there's a lot more boilerplate+blob data that goes into git today and git needs to evolve to support this.

I feel that once tools like Difftastic [1] and similar get more mainstream, and ideally more firmly entrenched within git itself, it will make code reviewing much smoother process rather than having to depend on Github or any other proprietary service.

[1] https://github.com/Wilfred/difftastic
A bit sad as the thing that made me decide to not even try their app (which looked cool!) was the abysmal performance (in FF).
I wonder what the blog author considers "high intensity"? 65-80% of MHR is common advice (see my other comment) but generally _not_ considered high intensity. 80% is still supposed to be under the lactate threshold.
How about `git status`?

The first SSD I bought back in 2008 was to put a large git repo on it; it helped. With much larger repos, like those I had to work with at Facebook, even an NVMe drive becomes a bit uncomfortable, and one has to use something like Watchman [1] to track changes without a rather noticeable delay.

[1]: https://github.com/facebook/watchman
>Git is line-oriented and has no notion of semantic diffs and semantic merges. This makes it a raw tool when working with, ironically, source code.

Git is a content addressable snapshot system, with bolted on code to make it retrospectively appear to be a line-oriented system.

It's worse than you thought.
Yep. It's a big deal because of how common it was.

In Germany, email is not considered as "in writing", and that's why so many things must still be sent by post. Most of the official bureaucracy is still done this way.
Some US movies made it big in Japan; others didn't, or never went there for whatever reason. (Hell, I grew up in the UK and there are plenty of american cultural touchstones that sank without trace there, or bands that are known in one country for something that's an obscure deep cut in another). And those movies that did make it into pop culture in Japan were generally dubbed and may even have been cut. So I think it's pretty much the same situation; after all, Robotech was on TV in the US since what, the '70s? And conversely there were certainly plenty of nerdy collectors passing around pieces of obscure cinema (whether US, French, Soviet...) on tape in Japan.
Heh but look where the trends with vets and dentists are. This won't last for long!
> And do you seriously not see the need of rebasing?

Git user for a decade. I never rebase, not professionally and not in my personal projects. I merge the work of other devs, no matter how ugly their history.

I don't see any real problem that rebase solves, but I do see that it mangles history and makes troubleshooting e.g. git bisect much more difficult.
Here Comes the Sun – To End Civilization
> Listening to the lovely bells of Winchester, one of our great mediaeval cathedrals. So much nicer than the aggressive-sounding “Allahu Akhbar.” Or is that just my cultural upbringing?

- Dawkins
In my location in the US in the 70's we had poor TV reception for the station that carried Star Blazers and Speed Racer. (Some combination of our antenna quality and our location.)

It wasn't until cable TV reached my area in the early 1980's that I finally got a taste of anime, in the form of Robotech. Catching every single episode was a priority, because if you miss one, it could be years until you had another chance to see it. (I wasn't rich enough to buy VHS tapes for the series, even if I could find them.)
Don’t you think that law is a bit too convenient? Instead of individuals maintaining liability for their actions, now there is some legal entity to blame. It doesn’t matter what the law says. All of these amoral decisions are made by people.
Amusingly half of those things have been modernized to run on HTTP, so browsers can already do them.
This isn't a video game but it absolutely did the trick for me. Find a theme park with a lot of particularly scary rides, or a holiday town with a lot of "extreme" activities (bungee jumping, etc.). Precommit to doing every single one of them, ideally with a bunch of friends to hold you to your word. And then do them. Don't allow yourself any excuses, especially for the scariest ones.

These kinds of activities are designed to be scary to your monkey / lizard brain, but also to give a consistent payoff in fun and social bonding. I did this for about a week for a buck's trip, and something clicked in my brain associating fear and reward. It lasted for years afterwards; it's been over a decade and I can still feel a shadow of it now. And as you're hoping, the benefits carried over into my professional life.

It makes me think that painful, risky male bonding rituals are almost definitely a feature, not a bug. They turn up in almost all cultures afaik (bullet ant gloves, anyone?). And being able to overcome irrational primate fear is good for everyone including you.
What a nice photograph of a D-Wave Rainier...
It's everywhere, it's predictable, it opens late. Great for long drives.
My idea to improve the issue is the following: an app asks for permissions and you as a user get two choices: grant the permission or grant mock permission. Mock permission gives access to some random data that like stock contacts/stock photos/whatever.

Every app is required to work correctly with the mock data or is removed from the store. You could even have mock folders in the photo app or mock contacts on your phone so you as a user can see how the app works on those without giving it access to the real stuff.

Example: a parking app asks for access to your contacts and ability to call, you give it a mock permission. It just works. When it tries to call someone you see info: "app XYZ calls mock contact A". When it tries to read your contacts it just gets a stock list. If it tries to tell you it needs real contacts you report it to Google and it gets removed.
This. As an untrained person, you can go for a walk with a 90 bpm heart rate and lose a lot of weight and gain strength and endurance.

The psychology is way more important for the average person than an optimal training: do something you enjoy doing several times a week.
13% of the population is on opioids, 6% are on gabaergic/genics, and 17% are on monoamine reuptake inhibitors of some form. There is plenty of room to grow.
Where are they trending?Curious if you can expand
Oh yes, negotiation is a strong argument in that context. One that makes or breaks a CTO's mission, me thinks, if that company expects a lean path to ROI.

A multi-cloud paradigm is also a great way to teach you about your application and about those clouds themselves. A good reminder that "implementation is where it's at", and "the devil is in the details".
Germany has similar services. In my opinion, they're just a band-aid
Check official documentation of the RP2040 and see if you like that. It's chapter 3.

https://www.raspberrypi.com/documentation/microcontrollers/
> "Just read this link" on a complex and controversial topic may be comparable to "Just read this religious tract".

That’s a ridiculous and unhinged comparison.
> Okay you can find the bits, but what about the screws? I was specifically looking for them a while back and turns out the vast majority of screws that I was finding at stores (home depot, lowes, various local places) were still phillips.

Home Depot / Lowes is at least 50% torx screws these days. They're impossible to miss. Not sure where you're looking, but I'm talking about the actual physical store.

Especially if you look at screws intended for decking/lumber, it'll be an even higher % than 50.
SQLGlot is great. We've used it to extend our FOSS probabilistic data linking library[1] so that it is now capable of executing against a variety of SQL backends (Spark, Presto, DuckDB, Sqlite), significantly widening our potential user base.

We implement the core statistical model in SQL, and then use SQLGlot to transpile to the target execution engine. One big motivation was to futureproof our work - we're no longer tied down to Spark, and so when the 'next big thing' (GPU accelerated SQL for analytics?) comes along, it should be relatively straightforward to support it by writing another adaptor.

Working on this has highlighted some of the really tricky problems associated with translating between SQL engines, and we haven't hit any major problems, so kudos to the author!

[1] https://github.com/moj-analytical-services/splink/tree/splin...
I take the view that if someone says they're having fun you should probably believe them. I've known people who talked about games like addicts, that they'd spend hours "playing" and the best they'd ever get out of it was feeling numb, but those were always "deeper" or at least bigger games (mostly LoL and WoW), not Cow Clicker or any of the similar games that emerged later.
Ask HN: Is Google That Bad?
So i tried duckduckgo and it was worse than google.
Is google really that bad?
For every feature X, there is a programming language Y that has had it for decades.

It's not a question of inventing it, but rather of making it mainstream popular.
The best alternative is to use Aurora Store. It's also the only way to use the Play Store without a Google account connected to your device.
I believe this pivoting example might be useful to scientists, support staff and postdocs in other fields as well (e.g., physics, chemistry, bioinformatics, material science).

A few specifics that might be useful for scientists that are considering transitioning to industry.

Pivot sooner rather than later. The transition might be a bit rough early on. In general, you can't get away with the heroic/cowboy approach that you can in a smaller academic setting. The interview process can be rough and might have a bit of RNG to it.

Aim to jump around every 2 years (3 at the absolute most) early on in your career. This will help make sure you're leveling up your skill set, getting those hard earned experience points and seeing different approaches to the software development process.

Be mindful of "infrastructure"-ish positions that might make it hard to get noticed. You probably have a high skill ceiling, but you are rough around the edges. It's essential to find a mentor that sees your potential and can help you level up (this might be challenging for remote positions).

At a minimum, you'll have an order of magnitude more job opportunities and mobility. Mobility in academic projects can be challenging to navigate. It can be easier to find a place outside of the academic space where your interests and skills will be aligned. Industry can also have interesting problems to solve.

I suspect that the current economic climate combined with the current clusterfuck housing market might create challenges for retaining support staff and postdocs in these academic/national lab driven projects.
Now that I'm running a terminal (wez) that upports sixel I'm always hoping to find more apps that support it. Looks like this one doesn't although it might be a good way of rendering the graphics.
At this point any two of the UK, France or Turkey could probably take on Russia by themselves. Turkey could probably do it by themselves.

None of them want to get in an expensive war. And Putin is probably bluffing about using nukes, but who wants to risk it.
If you don't mind taking a risk on a physical card game (and you have an extra player), you could try out Netrunner (you can print-and-play the excellent starter set from here: https://nisei.net/products/system-gateway/#bundle).

Pitch: You play as either: an elite hacker trying to break into the servers of megacorporations for fun and profit, or the inner workings of said megacorporation, trying to defend against the hacker.

The game requires you to take risks because it's a game about information control. You don't know what the corp will do to defend itself until you make a run at their servers, and corps don't know exactly how the runner plans to get in, or what they'll find when they do.
Using Firefox their maps are taking a long time to load after each pan and zoom. lol.
If a term is offensive to a group, at least when used by someone outside the group, it's always offensive when used to refer to that group.

While I can discuss the word "fag" without feeling a need to censor it, I would never use it to refer to gay people explicitly *. TERF is not the same - even for you, it was the term that came easiest to use, because there is no other word that describes feminists opposed to trans rights so easily without writing a whole explanation.

It's not an offensive term, except that many people find their sincere beliefs offensive. It's most similar to "socialist" as used on the right - intended to indicate someone holds offensive beliefs, but not offensive when used about someone who is, in fact, a socialist.

* except perhaps in jokes, with someone who knows me well enough to know I can't mean any offense, but that is a completely different discussion
"If you were a large company with significant academic and engineering resources, you might instead want to design your own private secure protocol that:

Uses encryption you control, so it cannot be bypassed by hacking the certificate authority,

Uses UDP to avoid having OS connection state on the server side, and

Uses a well-designed, known packet structure to improve throughput and reduce security vulnerabilities from HTTP/TLS parsing."

I think at this point they would have done well to explain why WebRTC data channels are not usable or incrementally fixable for the purpouse. It's SCTP tunneled in DTLS over UDP. Missing is just the home brewed encryption requirement which would generally be a no-no in security engineering practices.
There absolutely is version control for rewriting commit history, no fancy tools needed.

Start another branch at the point where you want to rewrite history; don't switch to it: `git branch original-history-branch`.

Now `git rebase` your branch to your heart's content. This branch will have the new, rewritten history.

The original-history-branch still has your old history, refers to your old commits and prevents them from being garbage-collected, just in case you'd like to reset your target branch to that state.
Yes, came here to plug Pijul as well: for distributed version control, the "first-class conflicts" of Pijul seems to be a step in the right direction.

For anyone who hasn't looked at Pijul, the theory part of the documentation [0] is well worth a read.

[0]: https://pijul.org/manual/theory.html
I’m not sure it follows that people thought “Libra/Diem/Novi” would be a threat to the payments business. Personally at the time I thought having payments be at the mercy of a ruthless data monetization cartel seemed like a terrible idea, and it could be it was shut down for reasons along those lines.
Related TED talk: https://www.youtube.com/watch?v=objP3E625Xo
> And do you seriously not see the need of rebasing?

Rebasing isn't actually necessary, and there's a good argument to be made that you should never rebase. Fossil (the version control system used by the sqlite team) doesn't have any rebasing mechanism: https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w...

(there are of course also very good arguments in favour of rebasing, but my point is simply that it isn't strictly necessary in a "complete" version control system)
Three 'immortal' creatures that have fascinated scientists for decades
The Google Photos app on iOS is still an egregious abuser of this, requiring access to all photos to run at all, rather than just selected photos or no photos at all. I’m still not sure why it would need that if I only intend on using it to access shared albums in the cloud, download photos, or view selected photos on my device, but it’s Google so I’m not terribly surprised.
I'd definitely buy Fat Bastard themed fireworks.
I work at University and I only publish Open Source (GPL, MIT, or CCBy). It would be hard for my University to claim IP rights after I published something with these licenses.
The client is fairly easy, imho. Did you mean setting up the infrastructure? Because yeah, hard to do properly
My impression was that drink driving is fairly uncommon and is frowned upon socially in the UK these days, obviously there will be exceptions and I can imagine in remote places where the risk of being stopped is very low, this still happens frequently. That said, I live in London so don’t drive regularly so I could be way off the mark, but I’d be surprised if drinking over the limit (>1 pint I guess?) was a common thing.
But nooo, I also want to send raw Ethernet and IEEE 802.11 frames from the browser! /s

There's always a baby that will cry for more. People have been begging for raw socket access and other "I just can't get my head around this"-shortcuts since they wrote their first "Hello World!", TODO-list or guestbook API. There isn't really anything you couldn't solve with the things there are now in every browser. What would UDP bring to the table other than more work to deal with it in that regard? This is nothing about innovation or technical limitations. This is just another case of "B- b- but I want it my way because that's how I always did it! :(".
Deeper understanding of the physiology and psychology involved in exercise allows for better recommendations in cases where the general advice can’t or won’t be successfully followed.
Some of it seems to be unwinding: http://www.ftc.gov/news-events/news/press-releases/2022/06/f...
In my humble opinon there just isn't much point to use GPGPU for normal computing. I'll give you an example.

https://blog.cloudflare.com/computing-euclidean-distance-on-...

during this work I was able to achieve:

- 7.5kqps on 40 Xeon CPU's (optimized avx code)

- 35kqps on V100 gpu

V100 is say $10k, Xeon 6162 is $3k. That means $0.4 per request on intel, and $0.28 per request on GPU.

This really is not much difference. I'd prefer to own more general purpose servers than hard to program proprietary GPU's.

Obviousluy, getting GPU's sometimes makes sense. There are tasks that are a better fit for CUDA/GPGPU, stuff that requires high memory bandwidth, doesn't do branches. Furthermore, while V100 costs a lot, 3080 is supposed to be only say $700, which changes the equation in favor of gpu.

But overally, modern x86 AVX is surprisingly good, and apart from very specialistic tasks, porting generic algorithms to GPU is not worth the effort.
Many of these countries are such that I'd not be very-very certain about their statistics reports.
This does have real world consequences for all those small players who were suckered into buying cryptocurrencies at the peak by the likes of Saylor, Thiel and Musk at the peak. Many lost their savings and many more will.

Re the market caps, these are a fantasy propped up by unaudited exchanges currencies like tether. So it’s unsurprising all that perceived wealth melts into air - it never existed.

Interesting that you think web3/meta/crypto are tied together and have a future when nobody wants to use them. They were simply vehicles for speculation in a very large asset bubble, now that the bubble has started to pop nobody wants these speculative assets but we haven’t seen capitulation in markets yet nor the end of fed rate hikes, so the pain will continue.

Re infinite growth and business interest in these three areas, I see no evidence of that.
Yes, there are still fulfillment issues, the Octavo SoC is nowhere to be found. As a product, the PocketBeagle is better and lower energy consumption than the Pi Zero. You could both power it and access it from USB, it has two CAN bus ports and 4 UARTs. I couldn't ethernet + power over a single USB cable to work on the Pi Zero, yes on the PocketBeagle it works out of the box. But then the Pi Zero added WiFi, the mode powerful and energy hungry Pi Zero 2 W, while the PocketBeagle continued to have fullfillment issues and it has probably gone past $50.
Solutions Architect Tips: How to Build Your First Architecture Diagram
ScyllaDB uses Seastar as an engine and the DynamoDB compatible API use HTTP parsing, so this use case is real. Of course the DB has much more to do than this benchmark with a static http reply but Scylla also uses many more core in the server, thus it is close to real life. We do use the kernel's tcp stack, due to all of its features and also since we don't have capacity for a deeper analysis.

Some K/V workloads are affected by the networking stack and we recently seen issues if we chose not the ideal interrupt mode (multiqueue vs single queue in small machines)