skysight-inc/HackerNews huggingface dataset:
Honestly this just makes me want to give GeoGuessr a go again. Back when, I jumped in and the first shot I saw was like "What? No-one could guess where this is." Now I know someone can, I realise the game is playable.
Yes, exactly the same thing.
It's interesting; I'm the kind of person who feels uncomfortable using something without understanding the shape of the stack underneath it. A magic black box is anathema; I want to know how to use the thing with mechanical sympathy, aligning my work with the grain of the implementation details. I want to understand error messages when they happen. I want to know how to diagnose something when it breaks, especially when it's something as important as my data.

I like how ZFS is put together. I've been running it for about 13 years. I started with Nexenta, a Solaris fork with Debian userland. I've ported my pool twice, had a bunch of HDD failures, and haven't lost a single byte.

I agree with you on most of the encryption stuff. That is very recent and not fully integrated and the user experience isn't fully baked. I don't agree on unifying zpool and zfs; for a good long time, I served zvols from my zpool, and dividing up storage management and its redundancy configuration from file system management makes sense to me. Similarly, recursive datasets make sense; you want inheritance or something very like it when managing more than a handful of filesystems. I don't agree on pool names (why anyone would want ordinal pool naming and just replicate the problem you just stated re sda, sdb etc. is a bit mysterious), and I don't agree on snapshots (to me this is like preferring commit IDs in git to branch and tag names - manually created snapshots outside periodic pruning should be named).

ZoL on Ubuntu does periodic scrubs by default now. Sometimes I have to stop them because they noticeably impact I/O too much. Periodic snapshots is one of the first cronjobs I created on Nexenta, and while there's plenty of tooling, it also needs configuration - if you are not aware of it, it's an easy way to retain references to huge volumes of data, depending on use case. Not all of my ZFS filesystems are periodically snapshotted the same way.
People keep saying that, but how exactly is the regulatory environment affecting tech in Europe?
The thing is about emacs, it makes you self-sufficient. You can always change any behaviour you want to, including this.

I've never used prelude before. I just ran it for the very first time and this is what I did to discover what to change:

C-h k <down>

Help buffer comes up for that key. It looks like it's bound to a lambda, which is actually a bit annoying as you can't jump to the definition or anything, but it's enough to see that it's in `guru-mode-map'.

Then I grepped the project for "guru" (I used C-c p s g because I figured out it was using Projectile and familiar with its default key bindings, but you could use M-x grep, M-x rgrep or just grep in whatever way you are familiar with).

I found this in the docs: https://prelude.emacsredux.com/en/latest/troubleshooting/#wa... (Note, I found and read this in emacs, in docs/troubleshooting.md, I'm just giving the web link here for convenience).

Basically just add `(setq prelude-guru nil)` to your init file.

Btw, for anyone wondering, to run these kind of starter kits "standalone", clone the repo and from within the repo run `emacs -Q --load init.el --init-directory=$(pwd)`. Otherwise it will try to use your actual init dir by default.
What is the benefit of this lib over hf transformers?
Will they throw the book at you or at the company?
Little deal.

Plenty of WASM advocates act ad if we haven't had endless attempts at since the 1960's.

Also doing kubernetes with WASM containers must be a bad joke, when comparing how managing Websphere 5 in 2005 was so much easier.

On the browser side, it is a convoluted experience versus using Flash/Code Alchemy, Java Applets, Silverlight, with Blazor/Flutter being the only ones that somehow come close to how it used to be 15 years ago.
Totally disagree. A bad design can pass all tests and appear high quality, then crumble under high load. Even quality is subjective. Most people would assume it means being good at every aspect, but passing tests doesn't not guarantee that.
The convertible debt sort of does work like that in theory ... except that the expectation is that the goal is big growth or bankruptcy while trying (in which case the debt is discharged).
I use Restic and backup to rsync.net for remote backups. Works great.

I'm not working with much data though so even if I wanted to I couldn't get a ZFS send/receive account with rsync.net. I like the way rsync.net give you separate credentials for managing the snapshots. This way even if my NAS gets compromised i will still have all the periodic snapshots.

For me privacy is my main concern and Restic's security model is good for me. The backup testing features are good too and rsync.net doesn't charge for traffic so these two work good together. I don't use the snapshots though because rsync.net already supports this via ZFS.
Yes, that's precisely what I've found, it works well but not when it's hot out and this summer has been particularly nasty in that sense.

I'm looking at a pair of leather-over-foam paddings integrated with the grips themselves like I have on a tandem where I noticed I don't have that problem. But that particular model has proven hard to find.
(For those confused: when not logged in, Twitter doesn't show replies anymore, only a single tweet, like if they didn't exist at all; it doesn't show almost any tweets on anyone's timeline also, except a few old random ones. Thanks Elon.)
Exactly, nobody flocks to housing on its own: people migrate to job opportunities. Which increase with population density. If you increase housing where there is already demand due to job opportunities, then you increase density there, and then you increase the job opportunities again, and thus you increase the demand even more than what you satisfied with the new housing.

It's not as simple as "build more houses!".
Your missing the key point that the incentives are different: the board are electing the CEO to protect their investment, not to be a popular leader.
In fact, the default integer promotions together with the requirement that unsigned int hold numbers until at least 2^16 is the main reason C code for 8-bitters is somewhat... stylized, to put it mildly.
> You have missed the point.

No, I think at least in large part, you missed the point.

> It has nothing to do with coding but everything to do with adding tangible value towards achieving an Objective Goal (Business/Technology/whatever).

As I understood _Bullshit Jobs,_ "adding tangible value" to some business that doesn't actually add anything of actual (non-monetary) value to the world is bullshit. There are whole industries that make billions of dollars, but everyone who works in them is still doing a bullshit job. (I often think I do.)
Does your user run your software with stuff mocked out? The reason for testing is getting ahead of issues before the user finds them.
Points to get my A, but if he needed help to grade papers or programs I would help. How did I get a 1400 line program typed in one day? I used the card duplicator, and only had to type in about 190 lines - while the lab assistants would come into complain about the rattling noise.

I wrote the program in the turbo pascal editor Setline numbering and then sorted it by colums. I tested it with microfocus, and it showed one bug and two typos. On to the card punch and the IBM compiler, and the IBM line printer. Finished In time to clean my card punch completely. It was the end for the card punches, and COBOL. Over the next few semesters a lot of people asked how I did the last program I one day, and I just showed them the column sort of the listing. You either wondered what use it was or you thought it was evil. The code was elegant...
You can't service those customers. Just as the Chelsea Truck Company can't sell its customers modified Land Rovers without buying a Land Rover first.
Regret isn't a reason for a restatement of the terms of agreement. If you think that you are going to need a lawyer or sue someone because you backed a Kickstarter short of being fraudulent I suggest you don't ever use Kickstarter at all. That's so against the spirit of what the whole thing is about.
I've run into a ZFS problem I don't understand. I have a zpool where zpool status prints out a list of detected errors, never in files or `<metadata>` but in snapshots (and hex numbers that I assume are deleted snapshots). If I delete the listed errored snapshots and run zpool scrub twice the errors disappear and the scrub finds no errors. Zpool status never listed any errors for any of the devices.

So there aren't any errors in files. There aren't any errors in devices. There aren't any errors detected in scrub(?). And yet at runtime I get a dozen new "errors" showing up in zpool status per day. How?
> If testing your code is hard it means your code needs to be factored better. Stop what you’re doing and fix the design so that testing is easy again.

Then again, another central selling point of having tests is that it enables refactoring without having to fear that you change the behaviour of the code. So, if you have a codebase without tests, you should write tests while changing the code as little as possible, and then refactor it.
I feel like the "floating" bits in the center of the ports will break like crazy.

If I put on my game theory/conspiracy cap on, it could be interesting to deliberately make that part of the port extra flimsy so Apple has an excuse (due to public out cry) to remove the port completely and go full wireless, both charging and data.
9front System
There's a parallel in the design world that remains under-discussed. In my journey as a small studio owner, collaborating with numerous startups, I've found that raw experimentation, while valuable, isn't the only path to innovation. A startup can conduct endless user interviews, much like a developer can persist with TDD, but at some point, the sheer weight of expertise begins to eclipse the utility of trial and error.

There's a pattern to human behavior, just as there is in company challenges; a sort of predictability within the myriad of unique use-cases. So, as much as startups are evangelized about "talking to users", there's an underestimated power in simply hiring seasoned talent.

I for example have a decade+ worth of experience designing B2B SaaS products. Many challenges have familiar contours and are solvable without the rigmarole of repeated experimentation. Just as TDD can be misinterpreted as a silver bullet for flawless code, so can raw user feedback for impeccable design. The nuance, often, lies in the marriage of systematic process and accumulated wisdom.
I agree with your first sentence, although I believe that niche is really small, so I am entirely unconvinced as to the benefits of WASM.

I am an author of a large ClojureScript app, which sometimes does need to do intensive computation. In my experience, the performance of compiled ClojureScript (it uses the Google Closure compiler in "advanced" mode, so the code is really optimized) is not a problem at all. What is a major issue is DOM manipulation: any time you touch the DOM, you run into slowdowns of two orders of magnitude. And that can't be magically waved away by WASM.

In my case, if I had a ClojureScript->WASM compiler, it would likely provide me with an overall perceptible app performance gain in the 5%-10% range, while introducing a whole range of interesting bugs and issues. Not something I'd like to use.
> Let me know if you’ve struggled with this and have ideas too.

I’ve seen in podcast players the option to “only keep X unplayed episodes”, customisable per feed. That could work for high volume RSS feeds too, or an “auto mark as read if older than X”. I’m not sure if any RSS reader supports those.

What I do is simply unsubscribe from more stuff. Cut the FOMO¹, embrace the JOMO². When I open my feed reader the goal shouldn’t be to feel dread of everything in there, but to have no more than a handful of things I truly want to check. Sources which post too often are prime candidates for removal, you can always add stuff back if you find out you miss them.

¹ Fear Of Missing Out

² Joy Of Missing Out
People have this aversion of treating code for tests as production code.

They spend time designing the architecture for whatever they are implementing but when it comes to writing tests, all of that stuff goes out the window and people just do whatever takes the least amount of time.

If you start treating tests as any other code, it should get easier to change as your implementation changes, and you'll get a lot more value out of automated testing.
I would pay 10 times that amount not to be in a lawsuit against a large corporation. Have you ever had to do a videotaped deposition? They get to ask you anything they want while you are under oath for about a day and they aren't very nice about it. And that is just one thing you are going to have to do for your measly couple thousand dollars.
The experience is worse than Java, .NET and BEAM application servers, while pretenting to have invented something new.
Suboptimal compared to what optimal society?
You are less likely to rewrite something that is proven to work and has absolutely no tests. At least in any company, which relies on the service (because chances to break something are high).
Bad (or very "smart) design usually crystallizes on its own - it is very risky to touch it even with tests.
Fair point on the {pool}:{dataset} thing. I just don't like that the same {pool} name refers to both a pool of vdevs and the top-level dataset on that pool. It makes it that little bit harder to grok the distinction. Perhaps there's a better way to emphasize that difference.
This still sounds like something incredibly simple compared to most actually difficult things.
I do.

It's common enough that it has an acronym (LAT), and name "Living apart together":

https://en.wikipedia.org/wiki/Living_apart_together

It's not super-common, anywhere, to the best of my knowledge. But it's also more common than you'd expect.
> more complex and thus they actually

I could make a similarly unsubstantiated claim that their chips are much faster than RISC-V ones because of that (of course they are unambiguously faster it's just that this is not the only reason).

And anyway if RISC-V is to become competitive it will have to become much more complex as well..
Monaco Deprecates Copper in Favor of Fiber
I'm fine with encouraging proper tests. On a base level, TDD encourages tests, so it's overall fine, at least in principle.

My main gripe with it is the second-order concern that it encourages testing practices that are frankly not very intelligent.

How you should approach testing depends on what kind of function you are testing. Pure functions of their inputs should be tested with property-based tests. If you have

bool isPrime(int n)

the whole rigmarole of "make a test that fails, then write the least amount of code that makes it pass" brings you to something like:

assertFalse(isPrime(1));
assertTrue(isPrime(2));
assertTrue(isPrime(3));
assertFalse(isPrime(15));

and so on, where what you really want is to say something like:

for all 1 < i < n . n % i != 0

This obviously works less well when you have to deal with the real world, but even in that case TDD leaves you with a patchy and inflexible approach.
No wonder, since Lua is interpreted and not a fast one at it, unless LuaJIT comes into the picture.
> resistance to voter coercion and vote selling

Thanks for mentioning that issue, it's something that I don't hear mentioned enough in online/distance voting debates (maybe it just means that I'm not involved enough, but anyway good to hear this mentioned). It's so critical and at the same time fairly orthogonal to all the encryption / zero-knowledge proofs / quantum resistance and other cool math that nerds love to nerd about.
TDD is a tradeoff.

TDD improves good design *for the user* at the expense of implementation design *for the coder*.

Because you write how the code is going to be used first, you're completely free of implementation constraints, so you can make it as easy as possible for the user to use your library/app/whatever. This makes it harder for you because now you have implementation constraints that you didn't necessarily have if you started without TDD.

That's the whole point of TDD.
Can second Greyhound. Hungry now...
But Dubai has very lucrative tax incentives and tries hard to be neutral about who invests. So whether you are Russian, Chinese or Ukrainian Dubai is a good option for parking assets without being asked too many questions.
> For older societies, who even counted as persons? Slaves? Babies? Prisoners of war? Outlaws living in the woods?

Is there any reason whatsoever to NOT count slaves and babies as persons? You can not count them as citizens or adults, but surely they are persons.
It's not an American thing. The same issue crops up in the UK with London, for example. If you move to London you know you're going to be hit by things like ULEZ or endless ideological propaganda ads on the public transport system because of how the people there like to vote. If you move to a village in the home counties you're going to have a very different set of experiences.

In the UK this is often disguised because it gets conflated with age: people want to live in the big cities when they're young, and when they're young they're more liberal. As they got older they get less liberal and want more space, so move out of the cities, so at no point does it feel like they're selecting where they live based on politics. But it does shake out that way regardless.

The USA is big enough and California far enough to the left vs other places, that even moving from one big city to another will yield noticeably different neighbourhood politics.
Like CLR plugins....
And the investors aren’t billionaires themselves? Do you think investors give away their money for nothing? What are you even talking about?
1. Sadly, nothing. I crave one that is a consistent source of interest. However, I find creative writing the closest. Short stories are acheivable and finishable before my passions wane; and a new, different short story feels "fresh" enough that it tricks me into continuing. I also like that it's more possible to pick up stuff after putting it down, in some cases. However, I will still drift from it and do other things from time to time.

2. I realise I enjoy the research part of a new hobby more than the hobby and I set a timer in my calendar so that if I still feel passionate about trying something in a months time I can spend some small amount of money on starting. I have never ended up spending the money :)
I agree that there is nothing that forces good design, but if you force people to take more time to think about the design, it increases the likelihood of good design.

Problem is that people don't either take the time to think about it, or they're not given enough time.
You are naive believing this solves any issues.
my bad. blame anxiety :)
Emacs is a relic, it can take weeks of configuring to get it anywhere near as productive as something like VS Code or Jetbrains IDEs. If you want to procrastinate for a few months it's the perfect tool.
Atmospheric absorption, spectra, units and code
I guess it's like "cars are fast because they use similar engines to motorbikes, which also go fast". Technically correct, but doesn't really provide any useful information we can learn from.
Partnership vs. Limited Company: Choosing the Right Business Structure in the UK
Partnership vs. Limited Company in the UK: A Critical Business Decision. Explore the best fit for your venture.
Thank you! So far my motivation can be summed up as "I owe it to my characters to finish telling their story" even though it's all invented by me :D
Fractal Patterns in Reasoning - David Atkinson, Jeanne Peijnenburg - 2012

https://projecteuclid.org/journals/notre-dame-journal-of-for...

> This paper is the third and final one in a sequence of three. All three papers emphasize that a proposition can be justified by an infinite regress, on condition that epistemic justification is interpreted probabilistically. The first two papers showed this for one-dimensional chains and for one-dimensional loops of propositions, each proposition being justified probabilistically by its precursor. In the present paper we consider the more complicated case of two-dimensional nets, where each "child" proposition is probabilistically justified by two "parent" propositions. Surprisingly, it turns out that probabilistic justification in two dimensions takes on the form of Mandelbrot's iteration. Like so many patterns in nature, probabilistic reasoning might in the end be fractal in character.
`compression=on` exists.

You don't need to know about SLOGs and L2ARCs. They're not super useful generally but people geek out a out them.

I know those were just examples and I don't disagree with the general point.
Uh you are mixing sensible suggestions (ashift=12 as a default, {pool}:{dataset} syntax, though it will be hard to change so late) with very, very opinionated ones, which break use cases you may not be aware of.

Naming pools after hostnames: I have pools on a SAN which can be imported by more than one host.

Weekly scrubs, periodic snapshots, periodic pruning: This is really the job of the OS' scheduler (an equally opinionated view, I admit)

collapsing zpool and zfs commands - sure but why? so you can have zfs -pool XXXX and zfs -volume XXXX?

No recursive datasets? I have use cases where it's very useful.

`zfs list` should show if a dataset is mounted or not, if it is encrypted or not, and if the encryption key is loaded or not: Fully agree!

Don't make me type disk IDs when creating pools: You can address them in 3-4 different ways (by id, by WWN, by label, by sdX etc), and you have to specify in _some_ way which disks you want to go there, so not sure what's the point here.

Store metadata on the disk so ZFS doesn't get confused if I set up a pool with `/dev/sda` and `/dev/sdb` references and then shuffle around the drives: Already happening. Swap a few drives around and import the pool, it will find them.

Some of your suggestions are genuinely OK, at least as defaults, but some indicate you aren't really considering much outside your own usage pattern and needs. ZFS caters to a lot more people than you.
Thai food is all around amazing, but man, nothing will top the Khao Soi in northern Thailand.

Dirt cheap ($1-$1.5) and absolutely one of the best things I've ever eaten.
Location: Ukraine (UTC+02:00)
Remote: Yes
Willing to relocate: No
Technologies: Ruby (Rails, Merb, Grape), SQL (MySQL, PostgreSQL, Vitess), NoSQL (Redis, Memcached), API's (GraphQL, REST), JavaScript (jQuery, Backbone), HTML, CSS, GIT
Résumé/CV: https://www.linkedin.com/in/homenko
Email: sergey@mm.st

Hello, my name is Sergii and I'm a Senior Software Engineer with strong knowledge of Ruby on Rails framework, and have extensive experience in web applications development. I'm fluent in several programming languages. For the last 10 years I have been working professionally with backends, but I'm also familiar with JS and frontends as well.
second the "check Your bike fit". In my opinion, the checklist is:

1. check the bike fit (probably the main problem)

2. add some mobility / core training (at some point if You bike long distance out of the blue without much training, some bits in Your body will simply break / strain no matter how good Your bike fit is)

3. in case of problems, look up the terms "cyclist palsy" and "ulnar / median nerve flossing exercises". It should help recover a bit quicker.

All that being said, I'm typing this with a pretty severely tingling median nerves in both hands. 1200km in 86h without much training during the season and with an improperly adjusted saddle (didn't mark the position before packing the bike for transport). Yeah, do as I say, not as I do.