HN user

sn

266 karma
Posts4
Comments181
View on HN

I got excited thinking maybe another one was going to be held, because it was a lot of fun to do! Oh well.

If I put my submission up on github, is that considered unethical in the days of LLMs?

This sounds like fun, but I'm not sure how changing build systems fixes the vendor problem. They will just ship their proprietary blobs built on top of this new build system instead of the old one, and will not change other behavior. Buying from vendors who upstream or minimally open source their work might help.

Yes, skipping builds from source can be faster, and, I don't know that you need to throw away yocto to do that https://rootcommit.com/pub/conferences/2024/elce/yocto-binar...

From the statement about "Caches builds so no piece of software is built twice." I'm guessing that the author has not enabled sstate caching https://docs.yoctoproject.org/dev/overview-manual/concepts.h...

I'm a little doubtful on the post's assertion that yocto is only needed for "deeply embedded regulated products." For products that have to follow the https://en.wikipedia.org/wiki/Cyber_Resilience_Act coming up, they will almost certainly need:

* SBOM management https://docs.yoctoproject.org/next/dev-manual/sbom.html

* CVE (or its successor) tracking https://docs.yoctoproject.org/dev/security-manual/vulnerabil...

* License management https://docs.yoctoproject.org/next/dev-manual/licenses.html

And I'll echo what some other folks have said here: if you don't need features like that, bundle your custom bootloaders and kernel with a binary distribution like Debian and call it a day.

There's a relatively easy technological solution to mold: buy a dehumidifier.

We bought two after moving to Ireland. Both have drainage hoses. One has a pump and empties into the kitchen sink, the other has no pump and the drainage hose empties into the shower. No more mold problems.

It's great marketing! But yes. He considers it an error to specify "Use the same knife for the jelly" even though it's considered correct to state "Wipe the knife clean before using it for jelly". The latter statement implies the former, and if you follow all the instructions both are not wrong.

I also consider some of the instructions to be under specified. For example, a piece of bread could be said to have 6 sides, but only 2 of those are helpful for making a sandwich.

I think this is partially restating "try smarter, not harder" with a lot more words.

I also think it's unkind not to recognize that we have limited time and energy and it's simply not possible to address everything all at once.

IMO the better takeaway is to learn to admit when we're doing that (deprioritizing a problem we don't have the resources to address,) rather than pretending there is no choice, so it occurs to us to revisit the problem if and when there are the resources to do so. My personal approach to this would be to add it a todo list with no assigned due date.

Also, I don't know who the author is talking about, but when I read:

"These are people who could successfully launch a product in a foreign country with little instruction, but who complain that there aren’t any fun people to meet on the dating apps."

I hear someone who maybe isn't valuing romantic relationships but also views admitting that as socially taboo, so they come up with an excuse for why they're not in a relationship. I don't necessarily perceive someone who isn't applying agency to all areas of their life.

With clothes, make it cheap so if you make the wrong decision it's not a big deal.

Also recognize you're engaging in the sunk cost fallacy by keeping clothes you don't actually want, and you're making the world better by allowing it to go to an owner who would better appreciate it.

Some more concrete ideas:

1. thrift stores

2. clothes rentals

3. clothing swaps

4. Buy the cheap version of what you think you might like (if it exists) first before buying the expensive version

5. Don't make your entire wardrobe trendy clothes. Make most of it relatively classic / basic and limit "trendy" to a subset of items.

The doctors had to be so certain that it was life threatening before acting that once they decided it was life-threatening, she was already going to die no matter what they did. And this is not an isolated incident.

The law has to allow for more uncertainty for the carve-out to be effective.

The way to do this is with MA3, not traditional AM:

https://www.federalregister.gov/documents/2020/12/03/2020-25...

"In addition, digital broadcasting allows visual and other metadata, such as song and artist identification, station identification, and emergency information, to be transmitted along with the audio content."

https://www.radioworld.com/tech-and-gear/upgrading-an-am-to-...

It looks like MA3 has a longer range:

https://www.radioworld.com/columns-and-views/guest-commentar...

For bad-3-corrupt_lzma2.xz, the claim was that "the original files were generated with random local to my machine. To better reproduce these files in the future, a constant seed was used to recreate these files." with no indication of what the seed was.

I got curious and decided to run 'ent' https://www.fourmilab.ch/random/ to see how likely the data in the bad stream was to be random. I used some python to split the data into 3 streams, since it's supposed to be the middle one that's "bad":

I used this regex to split in python, and wrote to "tmp":

    re.split(b'\xfd7zXZ', x)
I manually used dd and truncate to strip out the remaining header and footer according to the specification, which left 48 bytes:
    $ ent tmp2 # bad file payload
    Entropy = 4.157806 bits per byte.
    
    Optimum compression would reduce the size
    of this 48 byte file by 48 percent.
    
    Chi square distribution for 48 samples is 1114.67, and randomly
    would exceed this value less than 0.01 percent of the times.
    
    Arithmetic mean value of data bytes is 51.4167 (127.5 = random).
    Monte Carlo value for Pi is 4.000000000 (error 27.32 percent).
    Serial correlation coefficient is 0.258711 (totally uncorrelated = 0.0).
    
    $ ent tmp3 # urandom
    Entropy = 5.376629 bits per byte.
    
    Optimum compression would reduce the size
    of this 48 byte file by 32 percent.
    
    Chi square distribution for 48 samples is 261.33, and randomly
    would exceed this value 37.92 percent of the times.
    
    Arithmetic mean value of data bytes is 127.8125 (127.5 = random).
    Monte Carlo value for Pi is 3.500000000 (error 11.41 percent).
    Serial correlation coefficient is -0.067038 (totally uncorrelated = 0.0).
    
The data does not look random. From https://www.fourmilab.ch/random/ for the Chi-square Test, "We interpret the percentage as the degree to which the sequence tested is suspected of being non-random. If the percentage is greater than 99% or less than 1%, the sequence is almost certainly not random. If the percentage is between 99% and 95% or between 1% and 5%, the sequence is suspect. Percentages between 90% and 95% and 5% and 10% indicate the sequence is “almost suspect”."

It could be that you aren't tired of coding but you're tired of coding with those languages, or for those given applications.

I personally really like the embedded space or any other role where I can lay hands on hardware, even if that's servers or networking equipment. I've worked in a data center, on gunshot detection systems, and also computer or network-controlled lighting, vehicles, and herbicide sprayers.

SSD Endurance 4 years ago

What I have done, and will continue to recommend, is to not have all identical SSDs in a RAID - they should be a mix of part number or age.

A todo list is not a plan to get things done.

If you're serious about getting more done, tracking how you spend your all your time is worth trying as a starting point. It allows you to identify where your time actually goes and what you need to do to prioritize differently (and if that's even possible.)

I try to live a spreadsheet driven life. I have a workbook with a sheet for my todo items with due dates if applicable, a sheet for both prospective and retrospective time tracking, a sheet for things I need to buy, etc. all in one place so I can pull tasks in as part of weekly planning. The week usually doesn't go according to plan but I think I still get more done than if I didn't go through the process. Weekly planning also gives me opportunities to start over fairly frequently if I fall off the wagon.

Let's define unikernels as running under a hypervisor. If it's not, it's more likely to be called an embedded operating system.

I don't think unikernels are worth it unless you're running at massive scale. A realistic target audience is providers of serverless-style services, in which case you're taking a vanilla application someone else wrote and compiling it against a unikernel.

I also fall in the category of parler "was a haven for people who want mass executions for people like me."

I still think it's wrong to leak the data.

Many of these people use twitter and gmail too - does that justify a leak from those services? If not, why not?

There were and are legal means for law enforcement to access that data if they need to.

Public figures need to be sensitive to motivated reasoning https://www.psychologytoday.com/us/basics/motivated-reasonin... by the general public when they post. Looking at:

https://twitter.com/MLevitt_NP2013/status/130176837049748275...

What if he had ended this tweet with "But: I will take any FDA approved vaccine." ?

Except - he was at exactly 280 characters, so he couldn't have added this without removing other text, or doing a multi-tweet message.

https://academic.oup.com/joc/article-abstract/69/4/345/55470... says "We show that doubling the permissible length of a tweet led to less uncivil, more polite, and more constructive discussions online."

Maybe the character limits inherent in platforms like twitter cause many of the problems we're seeing right now, because people literally don't have the words to explain themselves.