skysight-inc/HackerNews huggingface dataset:
Unpopular opinion: every time I see anything made with LaTeX, it makes my eyes bleed. While it might be great for editing, I find it to be a pain to read. I really wish academic papers (and everything else it is used for) would be written with a tool that generate at least a bit more readable output...
I think the idea is that if a manager is just like... in the meetings with team members or also just ambiently participating in the work then they'll know what is happening.

I don't need a metrics dashboard to know what's going on with my spouse. Feels pretty normal for a manager to have a decent idea of what's going on with their reports.
I am open to the idea that it is possible, but many things are possible. I'm asking you to share information that supports your assertion. You still haven't done so. It appears you're dodging the question. Do you have documented examples or data, or not?
> Not requiring the cooperation of developers to opt-in, for starters.

True, meaningful in the general case, and completely irrelevant in this particular case, which started with specifically the question of OpenBSD applying the protection in question to its own base system. I actually agree that being able to externally impose a sandbox is super useful, but self-imposed restrictions are perfectly applicable in this usecase.

> You really think pledge and unveil are equivalent to sandboxing? Can you refer to any sandboxing solution or technologies that limit themselves to restricting syscalls and hiding file paths? Unveil is a lot more useful as a component in sandboxing, I'll give you that.

I think that pledge and unveil are a type of sandboxing, certainly. And... I'm struggling to think of any sandboxing tech that does anything but limit syscalls and filesystem access. After rereading https://github.com/containers/bubblewrap?tab=readme-ov-file#... a bit, I suppose there's a case for being able to change what a sandboxed process can see rather than only masking (ex. PID 1 is a different process inside and outside the sandbox), but that strikes me as a slight variation rather than a fundamental difference in what is or isn't a "sandbox" per se. Likewise, I could see an argument that OpenBSD's approach is coarser than it could be; ex. I think you could restrict a Linux process to keep your real user and be able to read files but not write them even though they're owned by your user and are 644, but that's more of a convenience thing than a true fundamental difference - an OpenBSD process could open files in read mode, keep the socket open, and then pledge away open() altogether which gives you the same outcome with more legwork.
For second chance pool reasons.. dupe of a future post from the same user (24 points) https://news.ycombinator.com/item?id=42014639
Sounds a bit unexpected from an information theoretical point of view: you’ve seemingly managed to remove this knowledge from the full 32 bit representation of the model, but when you compress it down to 4 bit the knowledge reappears. Makes you wonder what information was actually lost in the compression / quantization step…
I tried this a couple of years ago and had to ditch the TV because of too much input lag.

You mention input lag only once where you say:

> Although this post is mostly focused on productivity, most if not all 8K TVs can be run in 4K at 120 Hz. Modern TVs have decent input lag in the ballpark of 10 ms and may support FreeSync.

Have you measure this, or where do you get this number from?

The TV I bought was also advertised as low-latency, but I found it too high in practice (when typing in code, or scrolling, and waiting for the screen to update).
No I mean installing iOS apps on macOS on Mx devices
Of course. Same as helping a colleague (unless it’s a few minute task). Whenever there’s something that I can spend my time on, it’s going to be converted into a ticket.
As I understand the whole point is that it is not so simple to tell the difference between the model forgetting information and the model just learning some guardrails which orevent it from revealing that information. And this paper suggests that since the information can be recovored from the desired forgetting does not really happen.
Is nobody going to point out that the code will return that there’s a winner even when all 3 cells are empty? (Even with the fancy python chaining?)
When Arch Linux switched to systemd, my laptop (with an HDD) boot times jumped from 11 seconds to over a minute. That 11 seconds was easy to achieve in Arch’s config by removing services from the boot list and marking some of the others as supposed to be started in parallel without blocking others. After the switch to systemd there was no longer a such a simple list in a text file, and systemd if asked for the list would produce such a giant graph that I had no energy to wade through it and improve things.

Later, when I got myself a laptop with an SSD, I discovered that what my older Arch configuration could do on an HDD is what systemd could do only with an SSD.
doxing, the act of exposing private or identifying information on the Internet about an individual or group without the person’s or group’s consent, usually with malicious intent.
> An externally imposed sandboxing feature isn't necessarily less restrictive than pledge and unveil at all, although I'm curious why you think that is the case.

With pledge, you can read config files, open a file handle to your logs, and then completely drop the ability to open() files at all for the remaining lifetime of the program. How would you do that from outside the program?
It has been pointed: https://news.ycombinator.com/item?id=42038027
Looks very interesting - I have been looking for something exactly like this. Have just spent a few hours setting up a workflow with Instapaper and self-hosted Miniflux to get me to a similar place...

I'd love to try it, but the one thing that doesn't seem available yet is a quick way to save links (i.e. in the read it later workflow) like a browser extension, or, for mobiles, an app. Are those in the pipeline? Otherwise this seems a perfect fit for me.
Ah yes, that makes sense. Thanks!
This is an amazing archive of interviews. The audio quality is astounding — you would think these were podcasts from this week. I enjoyed the 1959 discussion with Arthur C. Clarke as well:
https://studsterkel.wfmt.com/programs/arthur-charles-clarke-...
> now I have to avoid that and minimise tinkering/hacking.

I think this right here hits at the crux of the issue.

There are people who like systemd because it's integration-tested with itself and its own defaults, so if you never change those defaults you don't have many problems.

Then there are people who don't like systemd because if you do have to change any of its defaults, it often doesn't go well. And, of course, the latter behavior as a box users are expected to live in is poisonous, because everyone is being conditioned to be passive and uniform.
It'll trip if you're drawing 10a sustained, you really can only draw 80% sustained to avoid a nuisance trip.
> Can you refer to any sandboxing solution or technologies that limit themselves to restricting syscalls and hiding file paths?

FreeBSD has capsicum and Linux has seccomp-bpf & landlock. Of the three, pledge and unveil are the least horrible execution of the same idea (though capsicum is alright, too).

Obviously it's not a "run any random machine code on my system safely" type of sandbox, rather it's used by e.g. browsers as defense in depth so that attackers can't just outright call execl.
Who cares if the ISP supports ipv6? Figuring out a world without DHCP and subnetting on a LAN is the hard part.
> that if industrial companies are doing well

Except it might be very hard to tell that because it’s effectively randomly weighted.

Caterpillar almost has the same weight as MS and double that of Amazon.
With more than 10, I tend to prefer the term department, though the term department could also be used for an organizational division with a smaller number of people.

The way Cloudflare has Departments on their jobs page fits my mental model of it. One is Emerging Technology and Incubation which sounds similar to GitHub Next. https://www.cloudflare.com/careers/jobs/?department=Emerging...

On the GitHub jobs page, there isn't such a selection, but in autocomplete there are two results for team and none for department or group: https://www.github.careers/careers-home/jobs
Middle managers do not create value directly. They can only create the conditions for value creation by others. They can do so actively, by understanding their team and making changes, or defensively, by protecting their team from threats.

If they are 100% busy with optics and reporting, the only thing they can possibly be doing is defensive work. At which point the game becomes clear - an organization so addicted to those approaches is actively suspicious of their own employees, trust has broken down, it’s everyone for themselves.
You are giving me “how” and I was asking “why”. No biggie but don’t really see why
This all makes sense once you consider health as a business. There is no great interest by business in a cure to this or that. However, an expensive perpetual treatment (lifetime service contract) is far more appealing - the revenue stream is superior.

What we call a 'health' industry is a misnomer - it is a sickness industry, like the ministry of defence is really the ministry of attack.

If you want to really get cynical, you can consider the possibility that a lot of treatments are not only unnecessary, but actively detrimental to the person receiving the "treatment". The person in future may develop diseases that will then open further revenue streams from what would otherwise be a healthy individual. This would assure a healthy pipeline of future revenue for the pharmaceutical companies.

Luckily we have government agencies to manage the pharmaceutical products we are given. Unfortunately, it is something of an open door policy as senior government staff are then given senior positions in pharmaceutical companies.

I'm sure it all works out in the end!
>> So, my new position on that sort of thing is: fuck them. Don't help them. Don't write tools like that, don't run tests to see if your teammates will take care of basic "service hygiene" issues, and definitely don't say anything substantive in a performance review. None of it will "move the needle" in the way you think it will, and it will only make life worse for you overall. "Peer reviews actually improve things" is about the biggest crock of shit that people in tech still believe in.

I know this is coming from a good place and good heart. However, even in 500 people organization this does not work. Peer reviews, championed by FAANGM and now adopted by everyone, are here to stay. If you don't do the work then someone else is ready to do that and take credit.

Also, god forbid if you sit in Amazon style performance evaluation. Only way to survive is you know someone. I have seen too many things at these evaluations. One quarter someone is HV+ or TT and in six months they are on PIP because manager changed their mind or Sr. Manager or Director asked them to.

Pro tip: Don't work at shit orgs at Amazon (FinTech, Prime Video) and don't work for terrible employers. You won't believe how much fewer stuff we need to get by. I used to think one need 200k+ to survive in west coast VHCOL (Bay Area, Seattle). However, I am surprised how far even 60k gets you with a family of four and one of the spouse staying at home.

Author is mostly right in spirit and I wholeheartedly agree. I just don't see a way for employees escaping peer review culture.
I'm not familiar enough to know if this is particularly well adopted with NetBSD, but the obvious way to do it that I could see is A/B roots, where the active system can only update the inactive root.

I suspect the actual most likely case is that it's meant for appliances where the running system doesn't update itself, and updates are accomplished via actions like "go physically replace the SD card with the new one".
> There would have been a time when people would have said that 32MB is a crazy high amount of memory

Those days are long gone though, for better or worse.

We live in the 2020s now and ram is plenty. The small computers we all carry in our pockets (phones) usually have between 4 and 16g GB ram.
Interviewer made a mistake, stop rationalizing.
> Do they do "great" ? Arguably no. They shut down a number of consumer facing locations, had a hard time recruiting, and compared to Mitsubishi and Mitsui the gap has kept widening. In their small/middle customer businesses they're starting to face the rise of GMO and Rakuten where the two other are too far ahead to even need to care about it.

The last year I can find figures for has Mitsubishi's assets -5.46%, SM -4.14%, and Mizuho -2.03% (so yes a decline in absolute terms, but that's the best performance in the top 10, and sounds like closing the gap with Mitsubishi and SM rather than widening it). I can't find a branch count but Mizuho has vastly more ATMs (around 4x as many as Mitsubishi) and that number is increasing. They've continued to make consumer-facing improvements recently like their wallet app allowing electronic money payment directly from you bank account, and English support in their main app. Of course like all of the big banks they're facing competition from the rise of the net banks, but as far as I can see they're doing as well as any of the big four, perhaps better.
Best news.
> Whatever the types are, Python will probably do something. Just not necessarily what you want.

Are you sure you are not confusing it with PHP? Python is not statically typed, but it is strongly typed. There is no implicit type conversion unless it's safe to do so (such as between a float and an int).

For example, print(1 > "foo") will raise a TypeError, and print("1" == 1) will print False.
> To replicate the performance of the DJIA

Why would you want to though? The ratios are entirely random.
Employee metrics is just a tool, as with any tool's metrics can be used for good or for purposely evil. So, it is how you use it to improve that matters-
In a workplace everyone has a responsibility to support and make a good work environment and to ensure what you are doing is profitable, ethical, sensible.
Drones with flamethrowers are used to de-ice power lines. Can’t see why an individual would need one.
I imagine that it's the expression of the knowledge that got removed from the 32 bit version, and some storage space was dedicated to know not to talk about certain things. For example, people know various racial slurs and know not to access or use that knowledge.

But say you or your AI model take a blow to the head or a quantization, maybe you keep the knowledge of X but not the knowledge that told you not to talk about X. In that framing i think it's pretty straightforward.
How about [[https://www.bbc.com][<<<BBC>>>]]?
Honestly I don't recall exactly because it's been so long since I set it up. I think I did something to make it hard to export/convert to doc/docx, and maybe even prevent or make it hard to copy test for certain blocks. It was just using some tracks for things you can do with the pdf format, but I don't have more information at the moment.

I'll try and dig in later and see what I actually did.
That article reminds me a lot this sentence from Daniel Benett : "How could a slow, mindless process build a thing that could build a thing that a slow mindless process couldn't build on it's own ?"

Source : https://youtube.com/watch?v=TTFoJQSd48c
I m curious why you suggested KeePass instead of KeePassXC. It's been years since I compared them and ended on the latter.

Also KeePassDX for android (there's an Iphone version to read db files as well) is a good recommendation. You then sync the database in the cloud you use (optimally nextcloud but since the file is encrypted even GDrive etc can work). The ability to have the passwords synced is very useful.

P.S. With a setup like this there's you minimize the risk of getting hacked because you are not using a password service and someone would need to compromise your device to get to the passwords (which is a given if they own your device anyway).
> Those are two different kinds of sandboxing.

I'm arguing that only one example is sandboxing, the other is imposing limitations but doesn't meet the definition of sandboxing.
1. you meant near clipping plane, not far

2. clipping is a GPU fixed function done on x,y,z axes separately, so it will always be a planar cut

3. the effect you're talking about can be entirely removed by setting the frustum's near plane to fit within your collision hull, e.g. for a spherical collider

function near_plane_meters(collider_radius_meters, width_px, height_px, focal_length_px)
return collider_radius_meters * focal_length_px / sqrt(0.25*width_px*width_px + 0.25*height_px*height_px + focal_length_px*focal_length_px)
end
> You evaluate the innermost (i.e. the tail) expression first, and work your way out to the head. As a sexpr it is a little more obvious that way: `(= a (= b (= c 5)))`

That's not true in Python though.

a = b = c = <expression>

is equivalent to:

temp = <expression>; a = temp; b = temp; c = temp

I don't know why that order of evaluation was chosen.
The knowledge wasn't removed, it's just the weights mean it would never be used.

Quantization changes the calculations, and now the knowledge is available.
Wonder if the study is freely available without paywall.
Shout out to my old ISP CenturyLink who participated in world IPv6 day in 2011

...Then decided that NAT64 was "good enough" for people who wanted IPv6 instead of just doing fucking dual-stack
By monitoring and intercepting what the program is doing?
Notably this approach is basically completely nonexistent in practice.
Isn’t the reason by chance how try-catch works lexically? I find that as another overlooked billion dollar mistake. It’s not that a happy path gets a crack in it, but the absolute monstrosity of a catch ceremony together with a scope torn between two blocks. “try {} catch {} finally {}” should be “[try] { catch {} finally {} }” absolutely everywhere.
It is possible that the candidate would normally use it from muscle memory, but got confused under the stress of the interview.
"someone who writes code" is very vague. For someone who writes code primarily in Python this behavior is less surprising than the rest that you described.
Not op, but ColorNote is good.
This worked well when the biggest technical advance that would happen across two generations would be a new style of beer tankard, and when the biggest social change was the old king dying and the new king being throned.

When the pace of change outstrips this, you develop Problems.

The entirety of 20th century history has comprised us wrestling with this.
I don't think it applies in this exact case (the base OS locking itself down), but in general:

> Furthermore, it's work that every user benefits from, rather than requiring an IT professional to reconfigure for each use case.

A distro could distribute, say, bubblewrap configs that automatically sandbox packages and every user could likewise benefit from that.

> What do you see as the downsides?

I think you're right that devs are best placed to lock down their own code, but if you don't have developer buy-in (or if they just don't want to make the effort or aren't available) then externally-imposed sandboxes are a lot easier for distro maintainers or end users to add after the fact than trying to patch the actual program source to do pledge+unveil or such.
There are a few exceptions to this, with varying degrees of justification:

1. An underperforming teammate when your personal rating is tied to team metrics. Which is a shit way to run a team.

2. You are a tech lead in a company where the career and level expectations are that you will assist in performance managing ICs on the team. Which is being a manager in all but name.

3. You truly care about the personal performance of these "slackers", which is a good sign that you want to be on the management track, but probably shouldn't be.

4. You have some strong external incentive like slackers directly impacting the values of your shares (and you own enough for it to make a difference)

5. You are a petty asshole.

I will never cease to be amazed how many people will fall into number 5 - but will insist they are doing it for other reasons.
Recraft can generate long text now
>> I have a very basic question which I usually ask in a interview which is to implement a tic tac toe game. I like this because the logic is straightforward and it helps to judge things like code quality / speed / conciseness etc.

"I like this because the logic is straightforward and it helps to judge things like code quality / speed / conciseness etc."

No, it doesn't.

Everyone who comes up with their own pet way of evaluating and interviewing thinks - nay has the unshakable belief - that their way of evaluating developers is 100% spot on. However it's always something they just made up, justify with plain old words and never science.
> inescapable psychological aspect to the Dow that is unique.

Sounds about the same as:

> that is reported on because people talk about it because it's reported on.

The unique aspect is that a randomly weighted index is just outright stupid however you look at it.
That may be why a common definition of cruelty is being unnecessarily unpleasant: the Lords/Ladies of Instrumentality would say, it's not me, this just falls out of the Lagrangian, and yes it was horrible yet I was but the instrument. (compare the original words to https://www.youtube.com/watch?v=y6m9SusjNYk )

The chinese note a tension between 霸 and 王 , do they also note one between 正 and 仁?

Lagniappe: https://www.youtube.com/watch?v=92WwPFDn_xM#t=90s
there are 2 types of embedded systems: those that ship 1 million units, an and this that ship 50. if you're shipping 1mil units, you need to optimize RAM size, but if you're only shipping a few, them it's not worth squeezing everything down as long as it doesn't break your power/cost target. there's a ton of devices out there that literally just use a cheap smartphone as an "embedded" CPU because that way, Google has already done 90% of your R&D for you
That is the Apple tax on everything the fruit company sells, they always push the margins as far as fans are willing to pay for.
Tautology: a statement that is true by virtue of its logical form alone (Merriam Webster). Fits perfectly the “a neural network that can't process text is less good at processing text that one that can”

> It's perfectly legit to discuss how a Transformer would perform if only the Self-Attention part was removed

It only shows that you don't understand the topic at all (but hey, you talked about closed-form solutions and quantum computing elsewhere in this discussion with others so why I am even surprised…)

> Insofar as the actual other networks you've mentioned they fail to beat Transformers

They don't “fail to beat transformers”, they beat transformers that aren't the state of the art and are less good that the ones that are. And that's not really a surprise given that they are more recent and have much less manpower working on them. I don't expect them to replace transformers until they make some hypothetic breakthrough that'd makes them significantly better than transformers. That's what path dependence is. But they are still a good illustration to the point that you don't need to have attention heads to exhibit the capabilities of LLMs. (Remember you set the bar at GPT-2 level, and they are far beyond that)

> because language comprehension simply cannot be done without sensitivity to word context

And these models actually have a way to represent context so this criticism completely miss the mark. That's really hilarious that you make this kind of claim in an HN thread about SSM. How come you have no idea at all about what a state-space model is and then feels confident enough to come and argue in the comment section…