skysight-inc/HackerNews huggingface dataset:
Also with heating?
So all the bubbles rising up way before boiling and the visible evaporation does not happen with distilled water? Hard to believe, I have to say. You would have to do perfect even heating of all the water, to stop the movement from different temperate areas. Microwaving it?
Global service doesn't mean no competition...
That is one of the 16bpp high-resolution icons that came with Plus for 95 and IIRC by default with NT4. So the most probable place where you would see that is NT4 desktop (and indeed it looked somewhat out of place).
"Miscommunication" was probably poor wording on my part. What I meant was that their experiences, like mine, probably involved years or even decades of poor experiences with heat pumps in cold weather, so they were assuming that heat pumps haven't significantly improved in that regard.
Newlisp actually revives ancient mistakes in Lisp history. For example, there is no lexical scoping -- and "contexts" are not a substitute for lexical scoping. Lexical scoping ensures that bindings introduced within a scope cannot leak outside the text of that scope, avoiding subtle bugs that may manifest with dynamic scoping. Hence, Newlisp's lambda isn't really lambda, like Lisp 1.5's but very unlike Common Lisp or Scheme (absent side effects).

Newlisp's default (and most used) FFI is also... dangerous. You simply import a symbol from a shared lib and it gets bound to a procedure corresponding to a C call to that shared lib. No specifying of parameter types -- and most platforms do not encode parameter type information in shared libraries in a standard universal way. (Things like C++ name mangling, and COM, only apply to libraries written within their respective ecosystems.) But don't worry. Newlisp trusts you to get the parameter types right, because Newlisp is for the practical Lisp programmer. Woe betide you if you don't, though!

Guile's (system foreign) module provides a similarly dangerous FFI, but at least you can (and must) specify parameter and return types when you import a foreign procedure from a shared lib that way, allowing for checks for parameter correctness at the call site, if not the import site.
Yes, it's what I wrote about in the last paragraph. If you can compute maximum stack size of a function, then you can avoid dynamic allocation with fibers as well (you also could provide stack size manually, but it would break horribly if the provided number is wrong). You are right that such implementations do not exist right now, but I think it's technically feasible, as demonstrated by tools such as https://github.com/japaric/cargo-call-stack The main stumbling block here is FFI, historically shared libraries do not have any annotations about stack usage, so functions with bounded stack usage would not be able to use even libc.
> I cant think off a single profession apart from the IT domain that does this

The dichotomy lies in the fact IT and programming are not professions.

All of the professions you listed, you have to go to school for. For most of them, there is a body overseeing training, qualifications and conduct of the professionals, barring them from practicing for malpractice.

How do you evaluate Bob, a self-taught, remote developer, with no public projects, with 10 years of experience in no-name companies? You give them a real-world task and see how they do.
Guillermo Rauch – Vercel, the Front End Cloud
A short test like this can remove them completely

If your goal is to remove the bullshitters wouldn't a 5-10 minute, slightly harder than FizzBuzz, test also remove them just accurately and save everybody a bunch of time.
A bit unlucky but mistakes happen and I think this is just incredibly unlucky. Not getting the heyforks out for this one.
I agree, but no sensitive stuff should be upstreamed.
You're mixing up matters of logic and fact (how old the universe is) with matters of personal preference (like what I want to eat, should flying cars fill the skyline of my city).

People can be trusted a lot more in the second category, which is generally also their right. If they have valid concerns that are getting dismissed, they're not gonna like talking to you.
> I've got actual paid work to do.

Well, see, many graduates or experienced job seekers don’t.
I agree. Prehaps my wording that civilian use has nothing to do with military was too strong. There were other examples of civial programs in the past (like RBMK) that complemented military use very well. I'm frustrated because this argument is used to bash nuclear power, but never other energy sources. In general it helps to have developed technology and energy abundance to develop military tech and any technology can be missused.

Civilian nuclear power is not needed to have a weapons programs, it can help tho.
You also need to add tests as well as decide whether to break the existing API, or to create a new function in the API, in which case you need to design it. Do you add room for future support for division? Exponentiation? Knuth's up-arrow notation? Logarithms? What about integer factorization and discrete log? What about factorial? Sooo many choices. I can easily waste 3 hours in just 1 hour.
> Warning: fopen(https://docs.google.com/spreadsheets/d/1s2eNqf5xpVX8j6LfnL6r...): Failed to open stream: Connection refused in /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php on line 1493 Fatal error: Uncaught TypeError: fgetcsv(): Argument #1 ($stream) must be of type resource, bool given in /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php:1496 Stack trace: #0 /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php(1496): fgetcsv(false) #1 {main} thrown in /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php on line 1496

Just open the file yourself https://docs.google.com/spreadsheets/d/1s2eNqf5xpVX8j6LfnL6r...
>MHTML is supported by most major browsers in some way

Firefox? What about mobile versions of browsers?
Obviously I agree with your sentiment that this was a foolish and in the end a not-actually-cheaper solution, just saying that I think that was the argument used by the people responsible for the change.

It's insane that PSU manufacturers still haven't standardised the PSU-end of modular PSUs to this day. Or at the very least, standardised within one manufacturers offerings.

But I suppose I know the reason, it's more profitable if people can't reuse cables but have to get new ones every time they get a new PSU...
Oh... don't buy EVGA then.

I haven't had to RMA a power supply yet, but I buy Seasonics that are gold or better.

Not sure I can hear those coil whines though.
Analysis of the views and infos of all the Lana Del Rey songs taken from genius.com
This is how I feel about Kawa Scheme. It has very good Java interop without all the... Clojurisms which are like pebbles in my shoe while I'm working. It's what I'd reach for if I wanted to author, say, a large web service from scratch.
4% is small. Why can't it be 100%? (i.e., the company is forfeit)

Sure, it'll have a "material impact" at only 4%, but a determined company could just do it anyway. This doesn't actually force them to stop.
How would I know that the task actually takes 30 minutes before scheduling as much time they say the process would take? I presume that when they say "come in for an hour of talk and a three-hour practical task" (which the point where I'll refuse) I won't even know the task and can't already assume that I can actually be done much faster.
Computing with JavaScript's Undefined (2020)
First LiveView – LiveView Playground v0.1.1
For a “first level” interview the time demand is probably unreasonable.

But if you’re already shortlisted, I don’t feel it’s an unreasonable amount of time for a relatively basic assessment like this before they commit to paying you a significant amount of money by employing you.
This is actually very good insight that makes me pause and ponder about its implications. Do you know any in depth research/paper on this topic?

Ordered data types are core to computers actually: arrays, heck even the memory itself. I always thought the list to be the most fundamental construct, but outside the neat world of computer, the real world is mostly unordered. Order is artificial, is indeed often not a given.
That is neither true nor idiotic.
FWIW Haskell is the only language in which I've been able to return to code that I wrote six months later and still understand it.
1) C-syntax languages

2) JavaScript family languages

3) C family languages
PyMiniRacer (original) author here. PyMiniRacer is definitely a way to run insecure code, but as pointed, the several CVEs in V8 require measures beyond "just" relying on PyMiniRacer to make it safe.

For the record PyMiniRacer was victim of a CVE itself https://nvd.nist.gov/vuln/detail/CVE-2020-25489 - a heap overflow, my mistake.

1. Total control over what APIs the user's code can call: you kinda got it... users can just do plain JS
2. Memory limits: you got it
3. Time limits: you got it, but the current model is unreliable when used at high levels of CPU and a high number of threads.

And thank you so much bpcreech for taking back the ownership of PyMiniRacer!
But all functions are blocking.

fn foo() {bar(1, 2);}
fn bar(a, b) {return a + b;}

Here bar is a blocking function.
WSL1 just doesn't work well enough. I'd never recommend WSL1 for anything. The extra nines in compatibility matter in development work if you have any dependencies in your projects.

WSL2 is also pretty good at giving RAM back to the host Windows. I guess you're really running thin on resources if this doesn't do enough.
> Fibers and async/await are backed by the same OS APIs

async/await doesn't require any OS APIs, or even an OS at all.

You can write async rust that runs on a microcontroller and poll a future directly from an interrupt handler.

And there's a huge advantage to doing so, too: you can write out sequences of operations in a straightforward procedural form, and let the compiler do the work of turning that into a state machine with a minimal state representation, rather than doing that manually.
I really wonder if this was worth the few thousand they likely saved. You have two connectors(PSU and modular cable) with cost of what 1 cent a piece...

And it is not like they could not be used in some other model later...
> this country stopped subsidizing the risk of building

In the given picture how much risk is being subsidized by the government? What form does that take? What about East Palestine, OH? Can we live near train tracks? What about Paradise, CA? Can we live near power lines? Blizzards can become natural disasters, is the entire area above the snow line now facing new rules for building?

> commonly wreck buildings.

I can't say much about those buildings right there in the picture, but some of them have clearly been there for decades.
Thank you!

Any writer or communities in this space that I could engage with to find out more?

Is the best way to just join a sales team?
That's pretty much what the original poster does in Part 2, although inevitably the actual source code is a little more complicated than that.

https://quuxplusone.github.io/blog/2022/01/07/memcached-inte...
i've been writing an interface like this called aesthetic.computer and trying to work out a full stack for it - i love the ideas in your writing
Friend: Open-Source AI Wearable with 24h+ on single charge
There are several issues with the study:

1. Replacing pass/fail accuracy with smoother alternatives (e.g token edit distance) could be a terrible proxy for skill, depending on the task.

2. Even by the authors' metrics, they _still_ find a few potentially emergent abilities.

3. Hindsight is 20-20. Yes, we can revisit the data and fiddle until we find transforms that erase emergence from aptitude plots. The fact is, folk used commonplace test accuracy measurements, and the results were unpredictable and surprising. That's the true notable phenomenon.

I think there's value in the paper. Just...don't take its conclusions too far.
(2022)

Form 'Part 2':

> This is a great engineering interview problem because it pretty cleanly partitions the candidate pool into three different types:

> Type 2 looks at the problem and says, “Ah! I know just how to do this! Multiplication is just like addition, except wherever addition does +, I should do .” So they copy-and-paste, change all the +s to s, and they’re done in 90 minutes. Candidates in this group stand a really good chance of being hired.

As a non-expert in C/C++, I would definitely be of type 2, but I would be too afraid to apply for a job to work on a database engine's codebase.
If you want to hide your heat signature, and you have the technological means to capture and direct your waste heat, you could simply radiate it towards your system's star. This is assuming you're producing so much heat that it would stand out more from a distance than similar but lifeless planets.
I had the same opinion as you about halfway through each of the books. I'd encourage you to read them again and this time try to read them to the end. With this series, perseverance is key.
I have also been pondering with similar idea. Instagram and Twitter style services could be created with an RSS or RSS-like file format. Biggest problem is content discovery, but the Internet has traditionally solved discovery problem by itself.

https://www.appelsiini.net/2021/decentralized-social-media/

RSS was really great and still is. I still read my blogs using it and ignore the ones which do not offer a feed.
Working my way through your blog post and it is so refreshing. Unfortunately my algorithm currently is showing me takes which are extreme on either end (like in your blog post).

> Technology’s largest leaps occur when new tools are provided to those that want to make things.

I love this sentence. And the general attitude of curiosity of your post.
I've never had such a panel interview in my quite long career and possibly never will. I'm not allocating a whole day for an interview, that job offer isn't likely to be that much better than the current job or other alternatives to justify jumping through such hoops.

If you want me to do work for you and judge me on that, I'm available as a contractor.
> I find it so interesting how many of the symbol used are with
objects that have or that will disappear from our lives.

It is interesting how iconography links to timeless design. Function
and appearance have a way of coexisting in good design so the "idea" of
something gets into semiotics.

Disk storage is a timeless concept. It's absent now but will no doubt
return in some new guise on the next wave of materials science and
storage tech.

The pen is timeless too.

Perhaps the weird one is the classic phone handset. My daughter who
never saw one except maybe on a cartoon, instantly knew what to do
with an old 1970s rotary I was hacking. The design "reaches out" and
suggests its usage. Partly that's our monkey brains that sees tools and
uses in everything.
I've used async in firmware before. It was a lifesaver. The generalizations you make are unfounded and are clearly biased toward a certain workload.
> It’s a weird example. How would a C library know about the fiber runtime used in Rust.

Well, if you green thread were launched on an arbitrary free OS thread (work stealing), then for example your TLS variables would be very wrong when you resume execution. Does it break all FFI? No. But it can cause issues for some FFI in a way that async/await cannot.

> I find this argument funny. Why don't you have the same issue with preemptive multitasking? We live with exactly this "issue" in the threading world just fine. Even worse, we can not even rely on "critical sections", thread's execution can be preempted at ANY moment.

It’s not about critical sections as much. Since the author referenced go to, I think the point is that it gets harder to reason about control flow within your own code. Whether or not that’s true is debatable since there’s not really any implementation of green threads for Rust. It does seem to work well enough for Go but it has a required dedicated keyword to create that green thread to ease readability.

> As for `await` keyword, in almost all cases I find it nothing more than a visual noise. It does not provide any practically useful information for programmer. How often did you wonder when writing threading-based code about whether function does any IO or not?

Agree to disagree. It provides very clear demarcation of which lines are possible suspension points which is important when trying to figure out where “non interruptible” operations need to be written for things to work as intended.
What surprised me was the UK MoD. 400,000
One of the creators has a thread on X discussing the project here:

https://twitter.com/kodjima33/status/1772011777066442819?t=x...
Interesting to see some individuals and seemingly individual police officers fined. I know it was theoretically possible but I wonder what the stories are there.
What kind of tail are we looking at? One like a bunny or something like a cat?
>Why do you assume we distroy ourselves?

Have you not been paying attention to the news? We have a major nuclear power constantly threatening nuclear war, and several very likely conflicts between major nuclear powers.
Were you expecting something different?
EVGA is notorious for missing diagrams in their PSUs. This is no surprise to me. I am using one but planning to replace it with a more reputable brand.
> async/await runs in context of one thread,

Not in Rust.
There is an experimental flag[0] in the .wslconfig which let's you set autoMemoryReclaim to gradual or dropcache. On my laptop I had good success with dropcache and on my countryside desktop with gradual.

[0] https://learn.microsoft.com/en-us/windows/wsl/wsl-config#exp...
Sigh... It gets tiring to hear about embedded from async/await advocates as if it's a unique advantage of the model. Fibers and similar mechanisms are used routinely in embedded world as demonstrated by various RTOSes.

Fibers are built on yielding execution to someone else, which is implemented trivially on embedded targets. Arguably, in a certain sense, fibers can be even better suited for embedded since they allow preemption of task by interrupts at any moment with interrupts being processed by another task, while with async/await you have to put event into queue and continue execution of previously executed future.
Maybe in earth's crust, but on a galactic scale carbon is more common.

But they're both one of the most common elements either way, so I think other properties would be more important.

The way the GP comment describes carbon-based technological life made out of transistors doesn't sound like the metabolize carbon to CO2 or would require a lot of water, though, which are two important markers when searching for life.
> As a highschooler, this looked so futuristic & colorful as compared to 2000/XP desktop themes & icons.

Exactly my experience. The first time I installed Linux when I was around 15 I was surprised how modern, "sharp" and professional everything looked compared to Windows XP.

(The default Windows XP design was really the beginning of a downward curve for Windows designs. Windows 98 looked like a tool, Windows XP looked like a toy, which is a shame because Windows XP was a vastly superior (and in my experience ridiculously stable) OS. I always used the "classic" Win 98 design).
The first problem with microwave beam is that it can be used as a weapon and will be treated as such. So I don't believe it will get over prototype test phase before being banned like nukes. Additionally the further you are going to be from such beam, the less energy you will get from it. So transferring any energy from the Sun will be extremely inefficient endeavor.

Another big problem with nodes in Dyson swarm is heat, or the inability to get rid of it. They need to be close to the star so they can get as much energy as possible so they will heat up by position, but also modulate this energy and transfer it further, which won't happen without loses. So nodes can be constructed on gigawatt output but in reality be able to do fraction of that, otherwise they would fry itself up.
This interface was perfectly acceptable in the 90s, and it's perfectly acceptable today. Dropping a big graphic with a large circle button labelled format would have been worse. I say this as someone who writes my fair share of aesthetic user interfaces.

My takeaway is different. If your "temporary code" is sufficient to solve the problem, then it may last 30 years. If it was an actual problem, it would have been fixed by now.
This comment is about some of the replies here. On the one hand everyone seems to agree that software engineering interview process is broken because it doesn't make sense to ask comp science implementation questions for an engineering job. On the other hand some people balk at having to do a 3 hour engineering interview...or take home tests or full day meet-the-team style interviews. Payment for interviews is a can of worms w.r.t legality, either that of you restrict your candidate pool to people not currently employed.

To those who refuse engineering intervies that take time - what is your solution?
Accuracy of the Tz Database
My thermometer says it's -5, yet water is liquid. To be more precise, covered with thin ice. And covered with (thicker) ice it shall stay all the way to -20 probably. Whatever technical correctness you throw doesn't matter to common sense logic.

And that is even if there is a technical possibility to lower the temperature of every water molecule to -0.0001 simultaneously and demonstrate that it instantly freezes the entire volume in an instant. It'd be irrelevant since none of us live in that lab.
All of them writing code that doesn't work for the other's little islands.

It sounds like the Discordian battle cry: united we fall, divided we stand!
Having paid restore costs due to user error in my home, it's worth it. I'm toying with offsite HDDs in the future, but still feel that reliability is inferior.
> Bringing internet connection to everyone on Earth is an incredibly important mission. Consider supporting this mission by joining SpaceX's Starlink team.

I wish I could too.
It still blows my mind that browsers don't provide features this out of the box.
At least for Germany there are cases, where police officers have leaked information about people that they have access to through their systems. Especially leaking data about political opponents to certain groups.
In the 2022 thread it was mentioned the time limit was either 45min or an hour and not three hours, same as any standard coding interview.
A fine sentiment, but (FWIW) it goes into a ditch when dealing with CJK.
I'm surprised this didn't get more comment on HN - I'm curious if people find the explanation to be convincing? Why would the system skip rollout control just because the date was wrong?

Is it likely that Apple would program "skip rollout management" based on the date and not on a specific flag being set?

Is this cover for an update to a heinous bug, or something?

Any thoughts?
They're not mutually exclusive as far as cost goes - quite the opposite (hence all the talk about "synergy" and "vertical integration" in enterprise spaces) - but you're right about consumer prices. I think what's keeping the consumer prices for Starlink down is that for the vast majority of its coverage it does have competition.

Much like how it's in Tesla's best interests for the US not to invest in high-speed rail (hence Musk's "Hyperloop" stunt to prevent an infrastructure investment), it's in Starlink's best interests for countries not to invest in broadband technologies (whether it's mobile networks or fiber). I'm not aware of any plans to dissuade governments from those investments yet but I wouldn't be surprised to see it. Presumably Musk is too busy with Twitter at the moment.