skysight-inc/HackerNews huggingface dataset:
> From content, parent reply is correct. ZoL was far ahead FreeBSD's native ZFS port, that FreeBSD devs found that is better using ZoL instead.

The FreeBSD fork also had a bunch of ZFS features that hadn't yet made it to ZoL as well as their own bug fixes too. I know this first hand from porting volumes between ZoL and FreeBSD.

FreeBSD didn't switch their code base and dump everything they had in their own fork. They switched upstream so that everyone worked on the same common code base and merged what was practical and kept any of their own OS dependent code separate. Just as I said in my previous post and just as the presentation you linked to also confirms. And for what it's worth, it's the OS dependant stuff that makes ZFS's experience better on FreeBSD than it is on Linux.

I also don't understand why so many people want to assume a negative spin on the story. Projects fork and change upstreams all the time when it's identified that there's a commonality they can share resources on. This isn't any different.
> we can't swap out our fleet fast enough

Average age of a car in the US is 12 years. The fleet gets swapped out naturally pretty quickly, and slight incentives would accelerate that. It's faster than swapping out electric generating capacity.
They are cesspools because they are filled with alt-right bigots
It's Pyston 2.2, not Python 2.2
This is an interesting idea, but I feel it's not calibrated right -- I'm an academic, so I'd imagine I work with many "domain experts" (if you don't think so, that's of course another valid discussion). I don't think "if you bet on the entire set of implausible-sounding ideas proposed by reasonable domain experts, you'd end up net ahead.".

I hear a implausible sounding ideas all the time. I think one of the main points of academia is to give people the chance to explore those ideas. But they don't turn out good "on average", not even close.
What is arrow function in JavaScript?
I thought it was fun for what it was, but that it was sold and pushed as something it wasn’t. And overall (just my opinion) lacking gravitas.

For one it felt too easy. Some of this was likely console controller vs. mouse - and so maybe not the game itself’s fault - but it felt like point-and-click turned into just click, making it more one dimensional.

And two, I felt less weight/permanence in character building decisions. One of my favorite aspects of d2 is specialized builds, that you can screw them up, and generally delaying spending skill/stat points until certain. I thought d3 character customization felt more cosmetic and like my choices ultimately didn’t matter as all builds were so strong. Like it didn’t matter how I allocated points on my tree in the same way it felt like navigation and attack, described above, had lost some nuance. And that seems off to me when every character pretty much plays as a gear-independent caster.
Your priors seem way off
It may not help with sleeping better but nightshift mode seems to make it easier on the eyes at night in my experience so still worth enabling I think
https://nautil.us/issue/29/scaling/why-alien-life-will-be-ro...
> What is mutable by default in Clojure? Nothing.

All data in Clojure inherits from java.lang.Object. I get what you’re saying, but in real life commercial projects, especially when you use libraries and Java classes, the code ends up with a lot of mutable things. You can never know if any function you call does mutate something without keeping all definitions in your head, and with 20+ people on the project, this is a challenge. Programmers of languages less sexy use frameworks to manage state and effects, but not in FP, which clojurians think they do.

> Imperative? What is imperative by default in Clojure? Nothing.

Please note that I’m not praising Common Lisp or Racket either - the same criticisms apply to them, except they ship with type systems. In Clojure IO is usually done by calling a function that does some (blocking) effect and returns something. That is programming in imperative style. In practice effectful functions find their way into programs, and taints everything referring to it. For this reason, clojure programs written by teams tend not to be as FP.

> Blocking IO. Ok. So you want JavaScript?

I for sure prefer to write a backend where no teammates ever introduce blocking calls. I once worked on a webpage which took minutes to render, because of blocking calls on the back end. It was a mess, after having been worked on for years by around 70 coders, including consultants for the biggest names in Clojurespace.

> Zero guarantees at compile time. Almost true.

Except for syntax errors.

These things turned me off: imperative and blocking IO and effects and no square framework to contain it, combined with zero compile time checks. It results in teams making bespoke solutions that other teams in the company (or even consultants from the famous players in the Clojure space) solving their code needs by meeting with the authors and asking for changes, having a ton of testing to make sure it does not fail in rare code paths, and having one guy on every team religiously adding specs in order to not go mad.
Net loss was $747 million for the year ended December 31, 2020 compared to $514 million for the year ended December 31, 2019.

https://investors.modernatx.com/news-releases/news-release-d...
I think part of the reason that we don't have such a function yet is that it is essentially a one-liner if you use decimal notation for entities:

function escape_html(s) { return s.replace(/[&<>"']/g, m => `&#${m.charCodeAt(0)};`) }

That being said, a built-in function would be convenient and faster.
I wish there was a way to opt out of all that sexuality/desire for relationships crap.

Not that biology will easily let you.
Another problem with concentrating in the industry in which one works (and even worse - the company for which one works), is that in the event of a downturn, both your job/career and your investments will be hit at the same time. Just when you need your investments the most, they will be worth less than you expected.
Clojure has an optional type system: https://github.com/clojure/core.typed

(note that Lisp is flexible enough that a type system can be written as a library)

There's also this for run-time checking (i.e., you won't get any help at compile-time, but functions called with bad values will fail in very clear ways): https://github.com/plumatic/schema
I don’t have to pay benefits and most overhead, which is 25-50% of what you think of as your salary, depending on your salary and geography, so that factor alone gets you to ~1.5x before any accounting for slippage, overheads that the consultant now bears (tax and accounting, marketing/sales, collections). If a consultant is charging less than 2x, I hope they’re thinking of it as a hobby or charity.

On the buying side, if I need a specialist wizard on a particular topic for a week for an acute problem, I can shop for skills and largely don’t care what they charge. I want my problem solved and whether it costs $10K or $20K to solve a wizard-scope problem, I literally don’t care so long as it gets fixed. I don’t calculate “well, sure they fixed my problem but I’m annoyed that they make $1M per year at these rates!!”
This reasoning is excessive extrapolation. Any civilization that master interstellar space travel must be far more intelligent than us. The rules followed by such civilizations may not be the same as the rules we know.
What’s the middle of “something definitely exists” and “nothing exists”?

Seems like it would err on the side of “maybe something exists” which doesn’t quite feel like a middle ground.

Replace UFOs with Sasquatch.

“Sasquatch exists and here is the picture and Sasquatch tracks to prove it!”

“You made that up. It’s a guy in a costume. Why can’t we find any single dead Sasquatch? Why are all the pictures and videos crappy?”

“Why can’t you meet me in the middle and at least admit it’s possible that Sasquatch exists??”

Personally I’m open-minded and find the topic of aliens quite interesting. But there isn’t a single ounce of convincing evidence and it would require a gigantic coverup with tons of complicit actors. There needs to be extraordinary evidence before anyone needs to agree to meet anywhere in the middle. Until then we should default toward it not existing. In other words, your null hypothesis is that it doesn’t exist. So far the evidence has failed to cause someone to reject that hypothesis.
This article didn't really live up to my expectations based on the title.

What I would say, based only on information that almost everyone should agree on (ie. public statements and a very small number of authenticated videos) is that there are three possibilities.

1. Surprising government incompetence

This would be the case if all reported military encounters with UAP's could be explained by misinterpretations and mistakes (possibly including failure to identify foreign adversarial technology), as people like Mick West propose, and the government has been unable to determine this.

2. Surprising government competence

This would cover scenarios where the government has either created the UFO phenomenon from scratch as some kind of disinformation campaign (for unclear reasons) or has secretly developed technology far in advance of the publicly known state of the art and has kept it hidden for many decades.

3. A real phenomenon unknown to science

This covers aliens in the broadest possible sense of the term as well as unknown natural phenomena that somehow seem to exhibit intelligent behavior.
Senior/lead SRE contractor here from the Netherlands, I can share my own motivation switching to a perm job: VISA. I'm planning to move to Canada with my family and for the right company I'm willing to go back to perm. Offering part-time, remote, extra vacation, bonuses also won't hurt.
Full time remote work. It shouldn't be required but it should be allowed. I don't have sympathy for companies who cant find good help because they want to limit themselves to developers in a 50 mile radius.
Tangential note, it’s exciting to see someone using MPS. It’s an interesting and possibly transformative software technology that seems ahead of its time.
>The idea of capitalism is that wealth allocation is 'fair'

Every system of power comes up with excuses for why it is fair and most are transparently self serving.
In my experience at google, vps don’t have corner offices.
> W3w's advantage is more in the small number of words required

Digits have ten words. If five and nine are confusing, imagine trying to guess if the person meant flower, flour or floor, and guessing according to their accent.

If one to ten is confusing, you can always find 10 or 100 very distinct words to replace digits or pairs of them. You could also press numbers on your phone's keypad, or even send them as morse or binary.
Mighty is a good idea, marketed to the wrong people. I mean, who wouldn't just upgrade their computer? New software is a cost, even if it's "free."

I'm sure there's a niche, though. Like low-paid workers needing to do a lot on their crappy personal machines.
This is from MySQLs C library.
There are a few options I can see:

The primary way is to pay more. Technical skills are in a (global) marketplace, and right now it is a sellers marketplace. If demand outstrips supply, this is the natural path.

That said, if you can’t match the pay of the top bidders, you need to provide an environment they can’t or won’t, and how you go about this is specific to individual target developers.

Some things I might consider being worth accepting a lower offer - the range of things others will consider are different, and I’ll be interested to read the other responses to this thread as they come up!

- Be up front about pay and benefits. The number of times I’ve seen “competitive market rates!!11!!” in an ad only to discover they are absolutely nothing of the sort is simply infuriating, and I won’t engage with any recruiter that won’t give an up front range, and concrete measures of how to be at the top end of it.

- Don’t use third-party recruiters. This is variable by country, but in the UK recruiters have a _terrible_ reputation. I’ve personally blocked over 100 of them by email and phone, and as a rule do not respond to them.

- Don’t do “dog and pony show” interviews. If I have to write code on a whiteboard, or even in an editor live on a call, or look at an extensive take-home test (anything more than a 15-30 minute task), I’m highly likely to pass for anything except an a top shelf package at a company I’m highly motivated to work for.

- Eliminate barriers to work being done. I can’t count the number of places I’ve seen where developers spend more time in irrelevant meetings designed to boost the sense of importance of a B team middle manager than pairing, or even getting individual tasks done.

- Have an altruistic mission, or at least one aligned with the ethics of the candidate. If your business reduces to “invade privacy to sell ads”, I’d be unlikely to be interested even at top end rates. If it’s something less sociopathic, it may be worth a second look even if the explicitly stated salary range is lower.

- Don’t attempt to control employee behaviour outside of working hours. This includes open source contributions without getting tied up with legal review, and over-reaching IP agreements.

- Don’t expect me to go to an office, and have top notch IT support for remote employees, whether that’s VPNs that work without screwing about, or a BeyondCorp-type model. Others may want to go to an office, and it’s important to support both models. The days of “you must be in the office weekdays from 9-5” are gone though.
I didn't ignore them. It may be clearer to write all probabilities above as being conditioned on "our best knowledge of the universe".

P(All intelligent life is organic | Our best knowldge) =~ 1

Who knows the actual P(All intelligent life is organic).

My point is that OP seems profoundly ignorant of "the facts of the matter" as our best theories describe them.

Such facts make D-AnythingOtherThanAliens vastly more likely than D-Aliens.

It is possible to "imagine" a world in which non-carbon-based life develops to an intelligent point (somehow with evolution...? adaption? ... organic growth...?)...

And it is possible to Imagine they develop space ships, can travel near light speed and survive for billions of years without severe issues (again: how could an intelligent life develop which "thinks on small time scales" enough to build ships, but not be severely affected by having to live for billions of years?).

And its possible to imagine such a species has been exploring the near infinite vastness of space for long enough to have found earth and contacted us in a bizarre series of ways that routinely have little in common.

Etc.

But this imagined scenario is based in exactly zero physics, chemistry, biochemistry or anything else.

That such a novel can be written weighs nothing on whether we ought actual count it as a possibility.
Perks that appeal to senior engineers:

* Low distraction work. As an employer you minimize rituals and ceremonies for things like Agile. You also put out less operational email unless the engineer is dev ops specifically. No mandatory endless meetings except those specifically about business requirements. Don’t waste my time mentality.

* Offer challenging work. Will I be solving real problems? In exchange for increasing your revenue I, as an engineer, have increased my capabilities and advanced my skills and capabilities. I don’t want to dick around with your framework and circle-jerk some React nonsense or some excessive tool chain.

* Allow for initiative. As a senior engineer allow me the opportunity or flexibility to refactor code so that I can save you more money than I am worth. Allow me the freedom to devise new solutions that increase your potential commercial offerings or internal automation.

Those qualities also are what differentiate seniors from juniors. Just let me write good original code and hold me accountable for it. Given the choice that is what I, as a senior developer, want or else I will go somewhere that maximizes most pay against least effort.
Who needs evidence when you have ideology.
Ask HN: Do you agree Platform setup takes more time than feature development
We are trying to identify the issue related to the development of any Product or Prototype. We would love to know what is your experience around the same.

Problem Statement: Product features are generally created, but it becomes hard and bulky in setting up the platform to deliver the feature.

If you are a product owner or a startup guy and thinking around how the survey would help? We are building a low code tool that will automate the process of setting up a platform to deliver a feature to the end-user. The feature could be anything.

It's like you have an idea, develop it. We shall take care when it comes to make the feature available to end-users.

If you can spare 5 mins from your busy schedule help US with the survey on https://bit.ly/3b6dlSL
It's Pyston 2.2 not Python 2.2. this Pyston version is based on python 3.8.8. See https://github.com/pyston/pyston/blob/f71f76ff3874970d71ed4c...
This.

I'm a senior engineer. I'm passing good at what I do.

When I left my last company, I started looking for work in a culture that has changed significantly since the last time I'd looked for work (I was at that company for 27 years).

It was a shock. The naked and unapologetic disrespect and ageism has been pretty crazy. I threw in the towel, after a few months, and I'm now working with a nonprofit, for no money, and loving it. You couldn't drag me back into the rat race with wild horses.

I'm quite aware of the value of my skills and experience. I was actually willing to work for half that, if the work was interesting. I have my retirement set. I don't need to work, if I don't want to, but I love to work. When I die, the coroner is gonna have to rub "QWERTY" off my cheek.

I'd suggest that having a culture of basic respect for folks with experience would go a long ways towards your goal. Maybe less of the "cultural fit" stuff, and the "Draw Spunky" tests.

Experienced people can make things happen, which is what we are really after. I ran a shop with experienced C++ programmers for 25 years, and got used to doing really difficult stuff, and regularly shipping our work. One of the shocks I encountered was how rare that kind of thing is.

Many folks in the consultant market are there, because no one wants them as employees, or insist on treating them badly, when they are employees. These are folks that can write their own tickets. They don't need to be treated badly, and would often drop their gigs in a heartbeat, if they found a culture that valued and respected them.

Here's a suggestion: Hire them at market rate. Make their experience with you a joy. Down the road, say "We can't afford to keep paying you this rate, but we'd be beyond honored to have you on our staff at half that rate."

You'd be surprised. I got one of my best and most loyal senior engineers that way.

There's the old story about the retired engineer that was brought back in as a consultant to look at a problem that no one could solve. Engineers on the payroll had been looking at it for weeks, with no solution.

They looked at the system for five minutes, said "There's your problem. Just do this...", and the issue was solved.

They then invoiced the company $10,000. The company responded, saying "You only worked for ten minutes! How can you expect us to pay that much? Please resubmit the invoice with specific line items."

The engineer resubmitted the invoice:

1. Finding the problem: $10
2. 38 years of experience, six years of school, so I could find your problem in five minutes: $9,990
The only group that improved was those who skipped phone use before bed and allotted sufficient time for sleep:

> For individuals who slept more than 6.8 hours per night, there was some improvement in sleep quality for those who did not use their smartphones at all.
I'm not sure this is necessarily a good rule of thumb. There are plenty of times humans need to be protected from themselves--that's why regulation exists to prevent fraud, etc. It'd be ludicrous for a single sales employee to override payments right into their personal account.

It is SOFTware so it can always be changed. The question becomes who can do the changes and when (which ends up being much trickier to answer)
Could that couple buy portable milling machinery and start selling finished lumber? My relative had someone come out to his land and turn his trees into finished lumber for his house.
It’s not the $7.50 so much as the $7.50 extra for zero hours.

So my calculus is “Would I rather make $300/week for zero hours worked or $600/week for 40 hours worked?”

So it’s not just a more money question, but a money vs time issue. It seems rational to me to prefer less money for no work. The problem is that it’s not sustainable as we’re adding debt to pay for it in the short term. This seemed important when work was impossible due to COVID, but now that we’re recovering it’s again possible to work.

Is there was a sustainable UBI plan to keep paying for this in the long term, that would be nice.
First, it’s not fair to say they “strongly opposed” native apps “not long before” the essay. Every iPhone model has supported native apps through the App Store. Yes, web apps was their original plan, but they announced their intention to launch a native SDK just three months after the original iPhone release. It took another thirty months before this essay was published, so in relative terms, at that time that original plan was nothing but a historical parenthetical.

Second, this is completely irrelevant to claiming that the essay in question suggests developing mobile apps with HTML5. That’s just flat-out incorrect.
Yeah. Also, Suhail Doshi, the founder of Mighty, is mentioned as one of the people who draft read this essay.
I've said it before and will say it again: One code review or debugging session gives an interviewer more actionable information than an effectively unbounded number of logic puzzles.
Contract is a instant no for me. I've done the math and haven't found them to be competitive long term after what the above commenter mentioned (and that's before all the headaches of actually getting paid). Most of my peers feel the same way.
Bootstrap 5 Is Out
In real life projects, you end up doing type checking at runtime, meaning you also need a test for the code path
> Indian pharmacies already disregard medication patents without anybody's permission.

Good on them. I wish patents on medication were disregarded universally.
I was actually surprised they were still selling them. Have barely heard a thing since the (amazing) α99 II - that must be six years ago at least. Aeons in camera years.
As someone who had depression for quite a while and basically wasted 5+ years of his life due to that, at least from my own experience I can definitely say that there would have been ways to prevent this depression which could've given me 5 productive years back.
During this time I wasn't working or doing anything productive.
But that’s the opposite of what the post said. The cliff is real and happens regardless of promo because everybody gets refreshes every year regardless of promotions.
Yes but it doesn't go from an hour a day on March 20th to 12 hours a day on March 21st, it's a gradual lengthening. The GP said that it goes from not sunny at all to very sunny suddenly.
Another good example of one-sided, abusive contracts. The contract fully insulates the seller from all liability while providing no value to the buyer. The only real recourse is if you're big enough to have a legal team to review and amend but that adds a certain amount of overhead
You, the customer, is the person who pays the employee down the road.