skysight-inc/HackerNews huggingface dataset:
Forced conscription is the sad reality for many countries.

I was conscripted. I see it as my duty, a part of my social contract, a way to pay back to generations before who put their lives on the line in the fights for freedom.

I was lucky it was peacetime, but I am fully convinced I would have gone anyway as a young person without responsibility for children and citizen of a country worth fighting for.

For me (again as someone who served in peacetime in a peaceful country) it has been both educational and a career booster at points, it seems around here there are (civilian) jobs were military experience, even just conscription, is seen as a a major advantage or even a requirement.
Qt Design Studio is buggy and heavyweight. It lacks integration with Visual Studio, has a bad integration with Qt Creator. It doesn't produce clean .qml files. Qt Designer (the one used for Qt Widgets) is better in those regards.

Anyhow, this might be a controversial opinion, but the best experience I've had with WYSIWYG UI designers was with Netbeans Swing Editor and VS Windows Forms Editor. The IDE integration was seamless.
I don’t know about recent ones, but in old ones you need to long press the wheel to get a menu to select what it controls, then select a mode, then adjust the temp.

And the media controls are a mess that changes periodically with updates.
Why is the sexual orientation of cartoon characters being pushed on kids though? Seems like something to be worried about if you're a parent.
I e actually never seen an office with that setup from startup, to mid and multi nat corps.
And the joke keeps on running
I find this disappointing (the lack of accessibility tooling) as Wayland felt like a good opportunity to factor in accessibility from the get go.

For what it's worth though, accessibility was mentioned as one of the improvement area for which Gnome got funding: https://www.phoronix.com/news/GNOME-This-Week-Homed

Not sure what it will mean in practice, accessibility being a large topic.
My current hierarchy of "yes" when judging opportunities:

- Hell yeah: can't find a reason to say no
- Yes: opportunity is OK (with some small risks), or there are skills I want to learn
- Yes, but: seems fine, but I need to mitigate my risks
- No: by default. I believe in saying no when the road to reach a yes seems too complicated. Also, I feel it's important to clarify: that is not a hard/definitive "NO" but a "too bad we couldn't make it; let's keep in touch if things change".
I am into lifting too, but I'm home gym with minimal equipment.
Regardless of the current rule, it really ought to be a violation. If it's not, all repos that care about star rankings are forced to start doing the same thing to compete, which eventually turns stars into a metric of which repos have the highest quantity of annoying problems that users want to report, rather than a metric of whatever it's supposed to measure.
> But I just can't replace real human interaction with remote communication. I just can't.

That's entirely fair. You work best in a particular sort of arrangement, just as others work best in other sorts of arrangements. Nobody is wrong here.
> if you're employing programmers and making them sit in an openplan office you're willingly and knowingly making their job significantly harder, and their day worse.

I think it’s more fair to say that they’re making some of their jobs significantly harder and improving the experience for others. Plenty of jobs aren’t interested in optimizing for anyone’s personal productivity and happiness — they’re optimizing for their business goals.

> There's a reason that many programmers prefer to work from home

I think there’s many reasons this seems to be true (I say seems because the ones who prefer it are very vocal about it and tend to (at best) shout down those who disagree) and maximizing productivity is probably one of those reasons that they’re willing to tell their employers.
Gotta say I chuckled when I read the headline.
Thank you so much for the feedback and suggestions:

> 1. totally encrypted/syncing etc (iOS in the roadmap ;)

We're considering offering an encrypted cloud service, or alternatively, integrating with Dropbox/Google Drive. Details are still being worked out but data sovereignty is very important to me so that will be an important design consideration whichever approach we choose.

> 2. Infinite nesting (indenting/outdenting)

While I understand the utility, this feature might detract from NowDo's core philosophy of simplicity. Our aim is to avoid complexity that might distract from task execution, though I'm always open to re-evaluating features that could enhance user experience without compromising simplicity.

> KeePass type standard that is "portable" in the sense your data is always soverign and extensible or whatevr

We're currently using a universal CSV format for easy import/export of tasks. Does this align with your expectations, or were you thinking of something different?

> Purchaseable/One-Time Large payment like $50-100 with abillity to tip or however one wants to supplement if they wish to support dev

Your suggestion for a one-time fee in the $50-$100 range, with optional tipping, is intriguing. Our initial thought was a lower price point ($10-$15), but we're open to exploring different models. The balance between accessibility and sustainability is key for us.

> Customizable font/ui text and display size. This is important, a lot of apps that offer these features in various mixed bags are usually annoyingly ant-sized and non-customizable

Excessive customization can sometimes detract from usability and design coherence. However, your point about text/display size is well taken, especially for accessibility reasons. We’ll consider this feedback carefully. Could you share if you find the current UI size too big, too small, or are you highlighting a general need for adaptability?

Again, really appreciate your feedback.
I will never actually experience silence, due in part to listening to loud music way too often as a kid. Music or other low-interaction media is better than the constant high-pitch tone I hear ~16x7.
Prior to GOMEMLIMIT being a thing, people would get themselves into this situation occasionally. Their steady state working set size is something like 2.1GB, but they want to fit into a 4GB container limit, so GOGC=100 led to OOMs occasionally. They would bring GOGC down to 10 or something (why not 90!?), and then they are running GC every time they allocated 10% or 200MB, and then their CPU profiles would show they were burning a lot on GC, because it's pretty easy for an RPC server to generate 200MB of garbage.

GOMEMLIMIT definitely improves things, taking the very blunt instrument GOGC out of people's hands, and does what they actually want instead, which is to prioritize GC only when you're about to run out of memory.

People dislike tunables like this, and rightfully so, but a similar problem exists somewhat insidiously in non-garbage collected languages. Calling malloc() and free() is not a zero-cost operation, and you can certainly waste CPU by calling free() when nothing actually needs the memory you are freeing. GC lets cases like "this is a CLI app, the system has 128GB of RAM, the working set size is 2GB, and it's over in 1 second" basically never do any memory freeing. You allocate as much as you need, GC never runs, and the app exits. That kind of optimization is actually pretty neat. But, for steady state servers that run for an unbounded period of time, it is inevitable that you are going to spend time trying to reuse memory that you no longer need, because the system only has a finite amount of memory. Then the compromises start to balance throughput with efficiency. gc + GOMEMLIMIT is a very nice compromise that is excellent for many applications, but no heuristic is perfect for every possible computer program.
Not really. The problem with companies is when there is wrong-doing, it's just pittance fines and ultimately, those fines are paid with other people's money.

I wish it was more impactful.
I've noticed they've started shipping packages via central Asian countries like Kazakhstan. I've assumed this is to work around this rate change.
Why does it work perfectly on X11, then?
> Also, no, almost no build plates are aluminum.

Ah, I must be misremembering, thank you.

> Not a problem unless you frequently swap between materials of different thicknesses.

Yep, exactly, I have a PEI sheet (with a magnet) and it has a smooth and a rough surface, and I end up swapping between them sometimes. I guess it doesn't really make any difference, since they're both the same height (as they're two sides of the same sheet), but, as you say, my magnet sheet ruins the Beacon homing anyway.
I like to paint, bigger and bigger canvases. Very inspired by Australian Aboriginal art at the moment. Check out Emily Kame Kngwareye.
I can't remember which model, by "gears" I mean reverse, neutral, drive, etc.
I get a robot, sans one arm, and "Sorry, this page can't be found."
Am I right in thinking this title is non-sensical? From my understanding of the article, "Firefox 121 ships with native Wayland support" would work better.

Firefox can't "default" to anything because it has to run atop whatever display server I'm running. I guess you could say it "defaults to Wayland" instead of XWayland, but I can't see that being the common interpretation.
But, what if you could make an SAT that is equivalent to evaluating years of performance at work?

https://huggingface.co/papers/2306.05685

This paper makes the argument that...

"Our results reveal that strong LLM judges like GPT-4 can match both controlled and crowdsourced human preferences well, achieving over 80% agreement, the same level of agreement between humans. Hence, LLM-as-a-judge is a scalable and explainable way to approximate human preferences, which are otherwise very expensive to obtain."

So, the Arena could theoretically be automated and achieve similar outcomes. Or at least, it could quickly determine a predicted-ELO for every model, which would be interesting to compare against the human-rated outcomes.
I want to try kiteboarding, lots of wind where I live.
All of the decent WiFi-only IoT devices I've seen bootstrap the process by acting as an access point of their own until they're configured. There are some opportunities for securing that initial connection better, like ensuring that the WPA2 key for the temporary AP mode is complex and unique to each device, but I haven't come across a fundamental flaw in the approach. Are you aware of any?

I'd prefer an out-of-band option, like "physically connect the new device to the IoT hub's 'new device' port to configure it automatically before moving it to its permanent location", or "scan the QR code on the new device, which contains a public key that the IoT hub will use to broadcast the WiFi credentials over RF", but I understand that at least for mass-market residential products, that's unlikely because it generally involves more components on each device.
> Sorry for the negative take here but how it's written it feels like you don't necessarily realize that some people do need deep work, and prioritize your quick satisfaction to other's focus.

I'm always confused by people who struggle so much with being able to quickly answer a question and get back to what they were doing.

Also, here you're prioritising your work over someone else's.

> I simply can't stand incessantly being asked questions, I view it as a type of interruption

Well, you are being interrupted. But you're being paid to be interrupted.
I have a friend who did that; he put one of these relays on the apartment's power panel, so the whole apartment was protected against voltage dips or too short outages. It might not be a common consumer item, but it's a readily available device, AFAIK commonly used to protect industrial motors.
I'm not sure you are talking about the same thing when you say "flow" that I think most of the other people are talking about when they say "flow".

Flow as most are using it here, also known as being "in the zone", is when you achieve a deep state of focus on one particular task, and everything else seems to melt away. You reach maximal energy and enthusiasm for the work. It is where you reach peak productivity and creativity.

Most people cannot just enter this state at will, and when they do achieve it cannot maintain it for more than an hour or two. Getting into this state takes 20 to 30 minutes or more.

When you are in this state it takes very little to knock you out of it. A ringing phone, someone talking to you even if you just tell them to come back in a couple hours, a beep from a messaging app...all of those can knock you out of the zone.

Getting back in after being knocked out takes another 20 to 30 minutes. This means that if you are getting one interruption or distraction every 30 minutes throughout your time at your desk it is unlikely that you will get any time in the zone.

>> In the same vein, an office with a door won't help at all if you have higher-ups who expects instant responses to any messaging/e-mail query every five minutes

> Well, if you don't answer instantly, then you are stopping them in their flow

In the case of a manager interrupting you they probably weren't in the zone. But even if it is someone who was in the zone that is interrupting you them having to stop and message you was probably enough to knock them out of it.

It will almost certainly be more productive for the organization overall for them to work on something else until you naturally exit the zone.
OpenTofu Release Candidate Is Out, GA Set for Jan 10th
IMO a judgement like this doesn't discourage anything, just reinforces that fact that breaking the rules is advantageous and fines are a small cost of doing business.
They’re way more useful in languages without static typing, where it’s easier to write or edit-in stupid bugs and not notice until the code runs. They’re not not useful in statically typed languages, just far less so.
As I understand it (parody RPG elements notwithstanding) HM was originally (and appropriately) based on 1e/2e and is actually playable (as much as those games were. I imagine enthusiasts of those games might prefer the originals for historical authenticity, but HM sounds entertaining and fun! And a sort of 2.6e, which is interesting (much as PathFinder 1 was a sort of 3.6.)

Hmm, according to wikipedia Hackmaster 5 was rewritten and is a "serious" game - which sounds like much less fun, even if it is more playable!
Mandatory how? Won't they just ship an uncertified adapter anyway?
That makes sense for a solo project, but there are three of us working on this so it's helpful to use CI/CD.
If the govt gets into housing the calculus changes. See public housing in Austria or Singapore.
If you're testing implementation details rather than contracts, you're susceptible to this. Make sure the unit yutare testing is the thing you want to observe the behavior of.
Well, GP did say:

> And it always turns out that the girl knows more.

Even had <i> always </i> in the statement. I don't think logically you and GP can both be in agreement.
I don't think that's a sidetrack at all. It's unfortunate that the midlife crisis (particularly for men) has been so thoroughly ridiculed by the intellectual classes and the entertainment industry.

It's natural and, I would say, healthy to become more reflective when you come to realize that you've lived more years already than you're going to live in the future.

And having some activities that give meaning and joy to someone just in and of themselves is an important part of living well. Like you, I've found myself bothered by hobbies I put down years before out of a feeling that I wasn't good enough, didn't have the time, etc. Good on you for getting back to both golf and piano!
I do not like how ready the big spenders in the Linux sphere are to push wayland into every crack, considering:

1. It consistently breaks closed-cource software that I need to use in education like Mathematica and MATLAB

2. It requires tweaking to work with Flameshot and related screenshotting software

3. It breaks emulation layers like Wine and Proton (or significantly decreases performance). This was a dealbreaker since I managed to move almost completely to Linux for gaming.

4. It does weird things with scaling. I used to use three monitors (two 1080p above one another and a 1060p to the side) and it always did weird things if I tried to span windows across it.

5. It still is not working properly on Nvidia.

There is a problem with these technologies where the leaders are reinventing wheels and making them square in the process, acting like past paradigms are completely useless and that you're ridiculous for even questioning the departure from status quo. And because big entities like Microsoft, Red Hat, Fedora, Canonical etc. spend money on them, the main users have little say in the features developed. Desktop finally got to a reliable and comfortable point with software compatibility and usability, but now we have a ton of people funded by the EmbraceExtendExtinguish crowd pushing a new desktop protocol stack that obviously breaks things.
> you can spend a little bit of time at the beginning to empirically measure the optimal number of threads, perhaps with some heuristics to compensate for noise.

I'd like to point out that there is a lot of stuff published on ArXiv; this appears to be a very active research subject. Don't start from scratch :)
> Seriously does everyone just assume that people in the 60's were that stupid?

Most people assume history is about getting smarter and better; That bartering changed to trade with seashells because currency is smarter. They don't understand the supply chain, and the difficulty of obtaining enough quantities of calcium carbonate to construct city walls. They don't understand that people can't economize on things they don't know. They think /dumb/ is synonymous with /ignorant/. Some do learn the difference, but choose to remain /stupid/ by assuming past people were dumb, instead of making the best out of what they had and knew.
The program worked! As I wrote, the test tried a rare error condition and the handling for that was faulty.

Updated the original to clarify. Hope that helps!
Frankly, I have no idea what your point is. Clearly patents aren't enriching the inventor of the thing being patented, and that's that.
Do you have a auction + continuous market as well? With same or with different granularity?

Europe has an day-ahead auction with 1h products and continuous trading with quarter hours as the smallest product (still varying from country to country).
Would watch the first 5mins of this netflix series before I got distracted and ordered a pizza and...wait what was I doing?
I have an unrelated (and most likely dumb) question about the article. When they talk about the inheritance relationship between 'Thread' and 'MyThread' in the example code in reference to the destructor methods, particularly here:

> Now, what happens when MyThread::singlepassThreadWork() uses a member variable of MyThread like foobar and we delete the MyThread object while the thread is still running? The destruction sequence is such that MyThread is deleted first and after that, the destructor of its parent object Thread runs and the thread is joined. Thus, there is a race condition: We risk accessing the vector foobar in singlepassThreadWork() after it was already deleted. We can fix the user code by explicitly stopping the thread in its destructor

What does it mean when they say 'the destructor of its *parent* object Thread runs'? I've always thought that when you inherit from one class to another and then instantiate an object of said class, they're just one object, so what do they mean when they make the distinction between 'parent' and 'child' object? When you have inheritance of say two classes, those would be two distinct objects instantiated in memory? Is there something I'm missing?
This is cool! The very best software-based tuning tech out there is probably in piano tuning apps; they cost hundreds of dollars+ and are specifically made to report on harmonics and other piano nuances.

Do you have any comparisons against other pitch detection tech? Accuracy? Delay/Responsiveness? I assume it's much more compute work than a handcoded FFT type pitch detector.

I think it's possible this would find utilization in the piano world if the output offers something new / something that can analyze what a piano tuning maestro can hear and make it accessible to a mid-tier tuner.
"This is described, and then the remaining expanse of the embedding space is explored by using simple prompts to elicit definitions for non-token custom embedding vectors (so-called "nokens")"

so they make new vectors
Human vision is strongly exponential in terms of brightness sensitivity. In photography we talk about “stops” which are powers of two of light intensity.

Consumer digital cameras around 2005 could see maybe 9 stops for a single exposure. Now they can do maybe 10-14 (which means they’re ~30x more capable of a range of light values).

Human vision can handle adapting to a much wider range because we don’t see with a single exposure. The iris adjusts, we saccade around the scene collecting data and mentally aggregating it. A good approximation is the iPhone’s panorama mode. It’s really recording video and adapting the dynamic range window as you pan, so the sun tends not to blown out the rest of the image.

The main point I want to make is that outdoor sunlight on earth is indeed a million times more intense in terms of lux, lumens, candelas, or watts, than interior living (say lit by a nightlight or candle). This works out to 20 stops.

- 100,000 lux outdoors on earth

- 0.1 lux finding your seat in a theater

So we can see already when the light is 0.0001% the power of “Earth, noon”. We could see Uranus.

Sunlight on earth is extremely intense! You feel it direct on your skin like being 2 feet from a fire. It damages your cells. It evaporates the sea and propels hurricanes. I’d we hadn’t evolved to live with it, we’d find it quite intolerable.
I remember this video [1] from bigclive about it. I had no idea it was so common to have live wires in contact with water. At least they are grounded sometimes?

[1] https://www.youtube.com/watch?v=cNjA0aee07k
Because, frankly systemd + gnome + wayland actually work well together.

I'm not a Unix grey beard, but I've been using Linux for a while (6 years at this point). I have literally never had a problem that was related to systemd. So all the anti-systemd rhetoric just doesn't seem to have much merit to me.

Gnome is frankly the most polished DE on Linux. I've used many DEs and have run DWM and Sway setups. They all have their pros and cons, but Gnome is fine in my experience. In fact, Gnome is the most the most like a Window Manger of all the DEs. You can pretty easily get a keyboard only setup with Gnome.

I've been on Fedora for the last 2 years and Wayland has also been fine. Stuff like screen sharing was annoying at first, but I can't even remember the last time I noticed I was on wayland.

So call me a Red Hat Shill or whatever, but I just don't see what the hate is all about with systemd/Gnome/Wayland.
There's an opportunity cost to having an expensive power plant just sitting around doing nothing during the day. Yes you use less fuel, but how much of the cost of power is the fuel itself vs infrastructure and other non-marginal costs?

So only if the total cost of solar is less than the marginal cost of gas would it make economic sense to replace gas with solar during the day.
This is true, but the closest example of this happening that I can think of is mandating USB-C for phones. I don't think governments have ever regulated anything like internet protocols.

Also the standard has to have wide adoption before governments would consider mandating it.
This has seriously diminishing returns.

If a tree falls in the woods, and no one is around to hear it, did it fall?

If your the only one at work, did you work? Are you going to optimize to others view of your work habits or are you going to optimize to outcomes?