skysight-inc/HackerNews huggingface dataset:
I'm surprised how little is said about traditional diets. It's like everyone has to have the same numbers, diet, etc. If they don't, then it's automatically statins or bust.
Right? I was hoping more people would be thinking about the genetic aspect of this and how we need to stop telling people there is that "one diet" everyone should follow.
It started out as the desire to have an Emacs experience while surfing the web better than what Emacs was providing.

On one hand, there are multiple similarities:

https://nyxt.atlas.engineer/article/article-how-can-i-make-e...

On the other hand... There are also differences:

https://nyxt.atlas.engineer/article/why-building-nyxt-instea...
I second this. I'm a huge Rust fan, and not really a Go fan, but if you're thinking about leaning both, it will be much faster to learn Go first. Spend a couple weeks on that, and then you'll have another data point to compare while you learn Rust. (Go also distinguishes between pointers and values, which will be a helpful concept to have under your belt when you start Rust.)
That would be bad, since that’d mean storing the data themselves, with an increased risk of data leaks. (There was a medical data leak as recently as today from a Swedish agency. The track record is unfortunately not good)

But the law is the law.
There are a few things to make things slow still. Try macros generating async code. That can go out of control and is a common case in tests.
Yes, it matters very much *if* the paper is in a reputable publication.
The reason devs still use `cd+ls` is because they're ubiquitous. But always great to learn new stuff like this (:
It's amazing how many people want to come to the US.

The process should be a standardized legal one, not one that creates a second class "undocumented" tier of sub-citizen.
Sounds like energy production recently. While oil was cheap enough we had no reason to invest in cleaner tech. Even the threat of climate change isn’t enough. It’s only when oil gets real expensive that we invest in alternatives.
>So the idea is to force 12 people to convince each other of one idea or the other.

You said nothing to contradict the GP. If someone is on trial, all they need is one of the twelve to not be convinced of guilt. Your phrasing of "force" that one person to change their mind is absolutely insane to me.
I usually use NodeJS and TypeScript, but I've been learning Rust as well recently.
Why would you want to appreciate any ads? More targeted ads based on your personal data means you can be better exploited. Whether you want to accept it or not, advertising works and does influence our shopping behaviour. Otherwise corporates wouldn't be spending billions of dollars on it. Targeted ads means corporates have to spend even less money to better manipulate us. In what world is that good for us consumers?
As far as I know, Microsoft is the only big company I know that uses a gigantic, generic, combined EULA for all of its services at once.
There is an unofficial support for Windows via WSL.

Check it out: https://nyxt.atlas.engineer/download
I wonder how they screened out people with eating disorders. It's not like you can just ask them, because part of the disorder is hiding the disorder.
True, but I'd say it's a staple of international/exported Chinese cuisine.
I would like to see one of those things wandering around my work office.
For the record, I am profoundly pro-nuclear, happy with living in France and if i was given a choice between living next to a nuclear reactor and a coal plant I would choose the former immediately (all other things equal).

I think there are basically two problems with nuclear safety:

- one is that a single incident is broadcasted everywhere, no matter if there are causalities or not. This is similar to planes: when one crashes and 200 people die it makes the news. We have in France about 10 people dying every day in car accidents.

- the second one is the nature of the accident. When you fall from a rooftop, well bad luck. The place you fell on is not unuseable for millenia. This may be (and only "may") be the case with nuclear incidents. Now, the newer plants do not explose like Chernobyl did, because physics is going to drive down the reaction. There can be leaks, even dangerous leaks, but they will be quite localized.

xkcd had a wonderful graph on radiation: https://xkcd.com/radiation/
You can say this about literally any criticism ever. I hate it and it blows chunks. It is the ultimate libertarian way of striking down any discussion: do not criticise, even in any small way, because it's a free market and you can just make another one, so never EVER even THINK of discussing anything.

I'm not saying that there should be some kind of totalitarian regime that enforces naming, I'm simply saying that yeah it kinda sucks that Rust devs tend towards cutesy names over ones that convey functionality.

This just seems like you're getting weirdly offended for no reason. Not everything is some kind of attack on individual agency. There is absolutely nothing wrong with me remarking on the state of Rust naming. The fact that you are conflating it to be a "big deal", which I never said it was, just seems like bad faith arguing me. This is just not something to get so offended over.
Point being? It's likely you got friends throughout the boroughs and not just Manhattan, unless you just came here for a job. 45 min one way, 1.5 hrs both ways, is nothing. Especially if it means seeing the people you love.

It's more or less 30 min minimum to get anywhere regardless of location and there are beautiful and interesting spots all over this city, not just Manhattan. Why not explore?
Worms was my brother and my jam. We would play it all the time, and would give the worms personalities, and sometimes even avoid using a weapon with one worm because another worm was the "expert grenade thrower" or ninja or digger or whatever.

The silliness, combined with the ability to rapidly traverse terrain (but only if you were skillful) was what made it fun, and more like a game than a math problem.

I can't recall whether we felt that the best of the series was Worms 2 or Armageddon, but they were in the sweet-spot of the properly-bendy ninja rope, and cartoony and funny but no weird 3d stuff.
I use Go at my job, and Rust in a few personal projects.

The "typical" Go nil-check would usually look something like this (no idea how code will look, apologies up front):

result, err := someFunction()

if err != nil { ...

It's nice that you're not having to litter your code with try/catch statements, or use a union type with an error value like in other languages, but the downside is that Go only checks to see whether err is used at some point (or makes you replace it with _), and it's possible to accidentally use err in a read-context and skip actually checking the value. Go won't prompt you that the error case is unhandled (in my experience)

In Rust, when you want to return a null-like value (None), you wrap it in Option<type>. To the compiler, Option<type> is a completely separate type, and it will not allow you to use it anywhere the interior type is expected until the option is unwrapped and the possible null value is handled. You'd do that like this:

var result = some_function()

match result {

Some(x) => handle_value(x),

None => handle_null(),

}

The compiler forces you to unwrap result into its two possible underlying types (any possible <type> or None), and handle each case, which prevents an accidental null value being passed to handle_value. Trying to pass result directly into handle_value would give you a type check error, since it's expecting a <type> but is passed an Option<type>. The compiler will also give you an error if you try to only handle the Some(x) path without providing a case for None as well, so you can't just accidentally forget to handle the null case.

(For completeness, you can also just do result.unwrap() to get the inner value and panic if it is None, which can be useful in some cases like when you know it will always be filled, and you want to fully terminate if it somehow isn't).

So in your case (assuming this is in the context of a video game), you'd make score an Option<i32> for example, then unwrap it when you needed the actual value. Generally speaking, I'd make the score returned from a saved game loading function be Option<i32> and make the actual score for the current session just an i32, then the function that handles loading a game save into the current session would handle the Option<i32> from the save file (defaulting to 0 when this is None), and we could assume that the score would be set by the time the game session is running so we don't have to constantly unwrap it within the game logic itself.
Of course it's no surprise that people who eat less weigh less. The surprise, I think, is that people who are underweight are relatively sedentary.

Maybe this is not that much of a surprise either though? I wonder how much of this has to do with muscle. BMI infamously ignores muscle mass. An interesting followup would be whether people with low body fat % are sedentary. My guess is that they aren't.

Side note: maybe there is a disparate importance of "Calories In" vs "Calories Out" for people who are under/over weight. Maybe underweight people should focus on exercise more, and overweight people should focus on eating less?
N'other silly one:

git log --oneline --decorate --color | fzf --ansi --preview 'git show $(echo {} | cut -d" " -f1)'

The possibilities, they are _endless_ !!11!1!
Speaking anecdotally, my body temperature tends to run above average and I have a body that is shit at throwing off heat. I have dark skin yet still managed to get sun stroke earlier this week in the Mediterranean because my biology prefers me lightheaded than sweating. Morning run in the snow and t-shirt, on the other hand? Easy peasy.
Oh, there is a lot of cool things already possible. Some users outside of the team are doing interesting hacks

Check this out:

https://nyxt.atlas.engineer/article/emacs-conf.org
The high bar for acquittal is what makes the hung jury rule look like a Double Jeopardy problem.
It's hard to think about because I feel like when they work I don't think about them at all. And when they don't work I think about and stew about them excessively. So the good cases I forget about completely and the bad ones are stuck in my memory.

SDLC is a frequent pain point. Often non-existent or hacky, e.g. export this giant XML doc and you can re-import it if needed. If any step requires clicking on buttons it generally leads to that kinda pain. Almost fundamentally, if I need to go copy paste or click on something for the product to work, I won't be able to automate it. Hence, it needs to be completely automatable. Similarly, if the config / set up / customization one does is obfuscated after it is specified it can be a headache to try to work around. Also maybe not the end of the world but many also decide to "handle" version control on your behalf, which can maybe be fine, but will also then almost by definition be divorced for your usual approach and processes.

On the last question, I think this boils down to how well can one operate at the surface level. It is not uncommon in these low code apps to have to understand in detail what is happening below the hood. So yeah, the top layer abstraction might be very simple in practice, but if working with it frequently necessitates me knowing how that abstraction will be executing it leads to an extra layer of complexity that has not abstracted anything. In a way they often function like a second language going through a translator: if I have to be considering the Spanish version the no-code cares about and also how and what it will be translated to in English under the hood, it's just extra confusing for perhaps little gain. What makes it extra pernicious is you can be operating entirely off intuition for what that under the hood English really is, rather than some open spec you can at least drill into.

Worst part here is I feel like this is really often something that will come with using the product. Often the use cases documented and sold really seem like all you'll need.
There is a specific dev kit which is used in training materials[0] (the training is paid, but the material is all online for free), but you can use Rust with any ESP32 (xtensa or risc-v based).

The main esp-rs github organization[1] is a good place to get started!

[0]: https://espressif-trainings.ferrous-systems.com/

[1]: https://github.com/esp-rs
This is just a side effect of hypercapitalism at play. Aspects of capitalism aren't bad, but when capitalism is the single biggest driving force of your society, things like this are bound to happen, because the endgame that gets rammed down everyone's throat is "making money is your life's purpose".

These types of things have happened across how many industries at this point, historically? Practically all of them.
I'd imagine that thyroid hormone modifying treatments without thyroid dysfunction could lead to other issues.
>> An AI device filled to the brim with sensors, cameras, GPS and with remote connectivity

>Is therefore filled to the brim with valuables that an old car doesn't have.

Because cameras and GPSes are expensive now? Is a phone more expensive than car from 20 years ago then?
API docs, examples and the revised book: https://github.com/bevyengine/bevy-website/pulls?q=is%3Aopen...

Strongly agreed on the need for better introductory material; the existing book is extremely incomplete.

> I don't have this clear. Are 5/6 teams actually building commercial games with Bevy, or they just planning to do it in the future? This is a crucial distinction.

I know of 2 released commercial projects, the CAD team, a few indie devs who have started and 3 or so small studios who are looking to start. There's a little thread in the Discord where I've rounded folks up: [Bevy in production](https://discord.com/channels/691052431525675048/995713618526...).
I tend to agree with the parent. I am a rather shy person who did not naturally talk much during meetings and I had to train to be able to elaborate on simple questions for hiring interviews, because that is what is expected in the interview process. The goal of a hiring interview is to find out as much as possible about you, not to get yes/no answers to pointed questions, and making your interviewers come up with more and more questions to make you keep going is sure to leave a bad impression and cost you the job.

People who talk at length during hiring interviews are not necessarily "people who talk at length in meetings", they are doing that because that's what hiring interviews are about. You are misattributing cause.
I've noticed logrocket churns out semi-technical blog posts on mass on all sorts of subjects. Take a look at what has been submitted from them: https://news.ycombinator.com/from?site=logrocket.com

There isn't much a common theme on what they write about. It seems to be a bit of everything programming related and usually fairly shallow tutorials.

My guess is that it is a marketing strategy. They write all these tutorials to show up in developers searches for technical problems and hackernews. Its gets them a little name recognition. I guess it's worked in that I know their name and what they do but it hasn't worked in that I don't have an extremely high opinion of their articles. I mean they aren't bad, one helped me out once, but they are never amazing.
I am mostly sedentary, and maintain body fat below 10%. It's mainly genetics, and probably 20% diet.
I would hope not. Just because I have a key to unlock a door does not mean that I did unlock the door. It just means when the door is unlocked, I'm one of the people that gets called in to discuss if I had done it or not.
Thanks that was interesting. But I'm not sure if there is a point related to the discussion in there or if this is just a tangential piece of trivia?
The problem with personal projects is they almost always lack the scale, complexity, or real world constraints/drivers that real work does. Helpful to feel like you're actually building something but it is kind of boring to build things without a team. I really do enjoy learning from others with different approaches and learning from pairing and mentoring more junior developers and having to explain why we are doing things. There are just so few repetitions at BigTechCos that its hard to get that there.
Long ago -- 2006 to 2011 -- google had a functional source code search engine: https://en.wikipedia.org/wiki/Google_Code_Search

I don't recall if it supported SourceForge and GitHub (2008) but it certainly included gzipped tarballs which were popular and prevalent at the time.
I wondered why she was referencing games such as Madden 2005
> when you argued with this:

did you forget something here?

> If you believe that it's not for a majority of experts are not to decide, and a majority of laymen are not to decide, and a majority of Americans are not to decide, then who do you think should make the decision?

Democracy. In our system of government we elect leaders, those leaders are responsible to the people who have elected them. This has been sidestepped in recent decades by appointing experts who have the ability to use the force of law without explicit congressional approval. This is unconstitutional and the supreme court in the past year has twice affirmed this view[0][1]. We can't allow our leaders to hide behind people that they themselves have appointed when those appointees make choices that may have disastrous consequences.

> most people understand that the CDC is a normal org like any other, or indeed, like any normal person, which tries its best to do what it can with what it has, and aren't expected to be able to predict the future

Funny they didn't mention that while making proclamations from on high. "I did my best" is of little comfort to someone harmed by their choices.

[0]https://www.supremecourt.gov/opinions/20pdf/21a23_ap6c.pdf

[1]https://www.supremecourt.gov/opinions/21pdf/20-1530_n758.pdf
Gaining muscle mass will often lead to a quick onset of obesity once you stop lifting.
I remember seeing the source code way too young to really understand any of it, but working out enough to flip a single boolean that controlled the sun. Usually the sun had a happy face, and if you hit the sun with a banana it turned surprised. I was very pleased that I was able to change it so that the surprised and happy faces were flipped.
>The only part that scares me a bit is the type system for what I would be afraid to have to recreate a Prolog or something similar

Creating the core of a Prolog interpreter isn't much work. It is like a 30 line program in Haskell. See chapter 4 of "The Art of Prolog":

https://mitpress.mit.edu/books/art-prolog-second-edition

...there is a PDF available under the "Open Access" tab.
now that some time has passed, here's the web app if you wanna check it out! https://emporium.atitlan.io
I felt really bad about your experience. Nobody should be treated that way. I also felt envious that you had seen the VLA. I've always wanted to see it but never got around to it. But mostly, I admire that you are able to see the good things while bad things happen. Most of us are not able to do that and miss all the good things that happen around us while we go through the bad experiences of life.
Russia is a multi-ethnic country and slogans like that are destructive.
just use "pushd" instead of "cd" - as bonus you get directories saved to stack that you can "popd", much like unix.
Both of you might be interested to check out "How to Invent Everything" [1] - it's even got flowcharts the kind you mention at the end! [2]

[1] https://www.howtoinventeverything.com/
[2] https://mohamadacma.com/content/images/2022/04/825235c6-665f...
> there is this underlying hypothesis that things that happen to the main chracter can be qualified as true or bad.

Vonneguts point is actually the opposite:

> In Hamlet, Shakespeare tells us we don’t know enough about life to know what the good news is and what the bad news is, and we respond to that.
I loved scorched earth as a kid. It was great fun. I must find a copy and play it again.
I often start my .bat/.cmd files with

@echo off
pushd "%~dp0"

e.g. no matter from where, ensure that the current folder is the folder of the .bat/.cmd file
If you haven't seen the Windows version of "command line only", it's kinda funny: https://youtu.be/wUTW7Z9p6tY?t=347
Just to push back a bit, the promise/allure of software engineering is that you can have massive impact with a small dedicated team. Eg. WhatsApp had ~20 employees and was delivering more messages than the global SMS system.
I know a girl who weighs about 100 lbs soaking wet. Very slim, elfish type. She also has very hot hands and she says that after eating a big meal, she feels super hot. I asked her if it was measurable and it actually was, she can go to almost 38 degrees Celsius while completely healthy.
I think he meant opium war in the same sense that Americans say war on drugs.
> I'm simply saying that yeah it kinda sucks that Rust devs tend towards cutesy names over ones that convey functionality.

Are you using Rust? If not, why does it matter what they choose to name their libraries. This is my entire point, you're coming in as an outsider criticizing something that is clearly not a problem to Rust devs.

If actual Rust developers are using them to the point where they're popular enough to gain (unwarranted, imo) criticism, then clearly they're working, silly name and all.

It's almost as if people care more about what the function a package provides rather than its name.
Oh so your problem is that when attempting to dynamically link to the standard library, you're missing out on the dead code elimination you'd get when statically linking. Rust doesn't have a stable ABI anyways, so you can't really share the standard library between programs unless you're really careful.
In a recently reported issue with an Apple Car almost running over a pedestrian, someone on HN asked why can't we simply add the code:

if (personInFrontOfCar) { halt(); }

The reason, of course, is the self-driving algorithms are all done with machine learning. The model is trained with a corpus of information and the result is a "black box." The programmer could not insert the above `if` statement if they wanted to, they could not modify the source code of the model as if it was normal business logic. Instead, they would have to re-train the model on new data.

This is what people mean when they say it is a "black box." There is no source code to edit, only training data that outputs an as-is model. It's similar to getting binary blobs, for eg Linux drivers.

In contrast, I could fork regex if I wanted and add an `if` statement in the middle of it, and re-compile it. It is pure source code. Same with grep.
So this game has been done and redone a million times, and is one of the first games I ever played on Bally Astrocade. I believe it was called Artillery? Does that ring a bell for anyone here? We didn't have the actual cartridge, but an eprom that had the binary flashed to it. My dad was into that sort of thing back then.
AI Dungeon lets the game illustrate stories as they're being generated
Minor nit: Sichuan pepper is not a chili pepper or closely related to black pepper. It's the husk of the fruit of a tree that grows in the region. It's not particularly spicy on its own - the appeal is the numbing, tingling sensation (called málà, literally numbing spiciness) which serves as a complement to the capsaicin-based spiciness that Sichuanese cuisine is known for.