skysight-inc/HackerNews huggingface dataset:
PHP has gotten a lot better. New APIs have been added on top of features like classes. And many of the worst of the older APIs have been deprecated.

It still works on the "new interpreter per request model". But that has advantages in the multicore world: everything is thread-safe by default, and will scale to N cores without any extra work (for shared state people tend to use something like Redis).

It's by no means perfect. But if you stick to the modern bits and use one of the nicer frameworks (like Laravel), then I think I'd prefer it over something like Ruby.
People buy a lot of consumable products on Amazon. People buy a lot of things and realize how much they like and would like another for another room in the house or something. You aren't thinking broadly enough here.
Ask HN: Is Wetware Computing going to make a come back with the rise of ML?
I was reading about Wetware Computing, https://en.wikipedia.org/wiki/Wetware_computer, and it seems like some of the bottlenecks at the time that prevented further study have been removed. I wonder if it is an interesting avenue of study again?
Fork My Code, Please
Aren't gifts _usually_ at the giver's expense? Anything else is a transaction, surely.

I think the only point being made there was that this gift is expensive but he's happy to give it. The way I read it, he's happy to give out free iPhones, but asking/demanding a battery-charging case and extra Lightning cable on top might be pushing his generosity.
Related: https://news.ycombinator.com/item?id=18538614
In my experience, this is pretty far from true. I've worked with developers who tried to cover all of these skill sets and instead of being good developers they end up being pretty shallow generalists. Research is a zero sum game and picking "everything" just means you have small amounts of surface knowledge for many topics instead of deep knowledge of a few.
I think its an arrogance of software people that because we had to do partial differential equations at uni we're somehow pretty well versed in the other hard sciences. This may not even be that fringe.
> Microwaves I assume refer to ovens, which use a frequency related to the nature of the water molecule.

They work using Dielectric Heating.

Water, fat, and other substances in the food absorb energy from the microwaves in a process called dielectric heating.

See: https://en.wikipedia.org/wiki/Microwave_oven#Principles

Also: https://en.wikipedia.org/wiki/Dielectric_heating
Not OP, but I suspect it's to either drum up interest for it and/or get more eyes on the code in the hopes that others will review it.
> You're asked for help often.

Could also mean you write unreadable code and, by extension, unmaintainable code.

> You're the go to person by the boss.

Could also mean you write unreadable code.
On the other hand, netops staff costs are a lot less... is liquid the right word?

Yes, $200/month is probably not any more than a couple hours/month of even a very lowly paid developer or ops person, once you account for benefits and overhead.

But once you needed to hire that person for any reason... their annual salary is already on the books. Giving them more work to do doesn't affect your budget. But another $2400 a year might. Yeah, if you can avoid hiring that person _at all_... but you probably had some reason you did have to hire a person or three already, and now you've got them.

The actual experience of working in a small under-resourced organization, in my experience, often looks like this.
It's either this or quantum computing. I feel it will depend on how fast quantum computing can be commercialized
I think the title of this post is great, but the body doesn't quite deliver. The best content I've found on this subject is this book:

https://www.amazon.com/gp/product/0932633366

It talks about the different between informative and motivational metrics - the former being just for awareness while the latter being intended as explicit targets for employees. While it's easy to bleed the former into the latter, there's nothing inherently wrong with measuring game-able statistics as long as the incentive to muck with them is minimized. Easier said than done, but not impossible.

The article is pretty dismissive of story counting, which is a semi-popular approach to estimation:

https://martinfowler.com/bliki/StoryCounting.html

(Anecdotally, we had someone look at our teams' previous sprints and found that # stories / sprint was more consistent than points per sprint over the time frame they reviewed. YMMV.)

The focus on velocity-related metrics seems smart - Git Prime did some analysis on this and found that frequency of commits was a useful measure:

https://blog.gitprime.com/prolific-engineers-take-small-bite...

I don't see how these are any less game-able than klocs though.
When We Were Kings
(about the famous "Rumble in the Jungle" heavyweight championship match between Muhammad Ali and George Foreman)
> how long we can maintain the status quo before those folks collectively realize just how numerous they are and how much change they can effect if they try.

My 2 Cents: America is FAR from Perfect, but do you bench Lebron because he only won 3 Championships? Change?.. Yeah, sure, some is worth a gamble--But fer christs sakes you gotta let James start!
True, but you can still formalize the sense in which the object is weird in terms of how long it takes the optimization routine to run. See Bennett's notion of Logical Depth: https://en.wikipedia.org/wiki/Logical_depth
The tshirts are cute :)
You are not entitled to make money off it, just like you aren't entitled to make money off that open source project you forked.

You are absolutely entitled to make money off of an open source project you fork. As long as your fork provides value you that someone is willing to pay for.
all that ML and still mr Besos wants more
There's also Laravel, which is more popular than both Django and Rails on a worldwide basis (https://g.co/trends/9CGj5). Rails and Django are more popular in the US where I hear PHP is not very popular...
I think if you are doing an excellent job with your project, noone has time for you[dev] , as they are too busy enjoying your project.
its like when granpa tries to get in on the basement gamefest with the kids.
let them play, your best contribution is to make more toys for them to play with and let come to you and ask for more.
Chrome and Firefox Developers Aim to Remove Support for FTP
Although, there's something to be said for some potential overlap here. A lot of Codes of Conducts are basically being demanded by people who're not a part of the project.

Rich's point stands up well in response to that sort of thing: if you want it so damn much, fork it, do it yourself, and leave me to do what I do best.

That's the true beauty of open source, that you can just fork, do it yourself, and there we are. If your project is so much better than the original, people will flock to it. If not, well, at least you could still do what you did.
My personal favorites:

> Open source is a no-strings-attached gift

> Morale erosion amongst creators is a real thing.

It reminds me of a project called aurman [1] (a great AUR-Client for Arch Linux). Due to the 'feedback' from the community, the main author went from loving to work on his project to hating it. In the end, he stopped the public development to protect himself from the negativity.

[1] https://github.com/polygamma/aurman
To a first approximation, as long as spatially-local fragments all take the same branches, you can get good performance from branching on GPU. What matters is whether individual threadgroups ("warps", in NVIDIA speak) have coherent branches. The rasterizer makes an attempt to schedule nearby pixels on the same threadgroup, mostly to improve memory locality, but also to benefit workloads like yours.

In your case, if your scene objects are relatively large and nearby rays all tend to hit the same objects, then per-threadgroup branch divergence can be minimal.
I disagree. Publish or perish includes time to triage issues, bugfixes, and new developer onboarding.

If logging is fubar'd then all 3 of those are impacted.

If you're pushing a PoC out the door. Sure, go on ahead and forgo proper logging. But if you're secured some form of series funding and need to scale. Fix your boat before you launch.
We may need permissions for our dependencies (cf. Android apps). Ryan Dahl already did this with Deno, specifically because he saw weaknesses in Node: network, environment variables, file system, sub-processes.

We may need reproducible builds and reproducible minification. If we want developers to audit their own dependencies, in case we deem that practical, packages cannot ship their own minified sources. Auditing the non-minified source is hard enough.

We may need (for-profit) organizations that audit packages and award their official seal which you can trust before you add or update a dependency.

We may need better standard libraries and fewer micro-packages.
And demand will only return when the price stabilizes. And because the price isn't stabilizing, demand isn't coming back.
I'm using Forth for real-time data collection, and have been very pleased with it's speed. I'm able to reliably and consistently grab sensor readings over a 500 uS period with an average jitter below 1.2 uS on a Cortex M4. Yet I still get the flexibility of a dynamic language. It's a nice environment after the addition of some routines (coded in C) for dynamically allocated arrays with better safety mechanisms. In my case I'm not responding to various user inputs, etc, but the cost of the inner interpreter appears to be on par with - or better than - various bytecode interpreted languages.
What’s interesting is I can only find one organization working on this, Koniku. I think i’ll look a little more deeply
No it's not ridiculous. If Facebook is paying you to work on anything, they are getting more value out of you than your salary in their tracking endeavors.

Would you justify working for the Nazis if it was on open source libraries to better enable tracking people?
Research Shows Genetic Link Between Alcohol Dependence and Psychiatric Disorders
The Human toll of instant delivery – NYT (audio)
I think you're right: sugar is the main cause of gaining fat and probably leads to inflammation and disease.

I've been learning about resistant starch, which is digested by gut bacteria into fat, rather than digesting into sugar directly:

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

I can't eat legumes at the moment because I'm experiencing leaky gut symptoms and repairing my gut with L-glutamine. But I've generally experienced an association between eating foods like oatmeal/bananas/rice and weight loss.

Here is one of the more contemporary videos I've found about these things (from SelfHacked):

https://www.youtube.com/watch?v=luna9RQsL1E

Also my personal belief is that excess nutrition causes disease. So you can consume much more protein/fat/cholesterol etc than the USRDA, as long as you are physically active. Being sedentary kills. My own experience is that weight training is several times more effective than cardio because it burns calories as you recover.

Also this is all hormonal. So actively lowering your cortisol by avoiding stressors and increasing your testosterone and growth hormone with nutritious food and moderate exercise is a big part of why people drop 10 pounds when traveling outside the US.

Disclaimer: I have no evidence of any of this, these are only additional data points for your own research.

Edit: based on https://en.wikipedia.org/wiki/Resistant_starch#Nutritional_i... I'm going to try overnight oats. Basically steel cut or rolled oats (NOT instant oatmeal - it's already cooked) soaked overnight to preserve its resistant starch content.
And therefore you are ultimately responsible if any of those dependencies leaks your users data or compromises them. Just because that's how you choose to work doesn't absolve you of those responsibilities.
Having been able to provide all the infrastructure to developers, I find a lot of things on the 'production grade checklist' are not even on their radar. And I think we have pretty good devs. Logs, backups, HA, scalability, testing with production sized datasets, testing with production sized load. We found it better to empower our sysadmins to get involved with development, rather than the devops approach of empowering developers to be involved with deployment (we do both).
Customer service is hard. When you aren't paid for it, it is very frustrating. It often manifests as anger from open source contributors.
It's implied in the article that 300,000 lines of code is the total written by the company (of which the author is a founder), not by the individual author. With a company that's 3 years old, 41 man-years implies a staff of roughly 15-20, which is quite reasonable for a startup.
Yes, it was accidental. But I had a good laugh. Thanks
Well that was better than SourceForge. SourceForge actively added crapware to open source code.
The issue with configuration management is it creates a DAG above a build system that does the same, as in its superfluous.
The thin red skins from peanuts was another one from my childhood. Turns out they burn hotter than thermite and don't get you high. Not recommended.
“He says his goal was not to cure or prevent an inherited disease but to disable a gene, called CCR5, that forms a protein doorway that allows HIV to infect a cell. People who inherit this trait naturally resist HIV infection.”
Mandatory only to transfer to the new role, not for remaining employed. However, the program this person was in was finishing, so it was either take that or stop working there...
And I believe all were built by Lockheed Martin?
> But checkin had always did the same thing

I bet you have no problem in remembering what git pull, git checkout, git add, git commit and git push do, isn't it? For everyday work it's enough. You have problem in mastering git, all these nifty logs, diffs, indexes, refs, heads, remotes and other stuff. Other VCS have complex concepts too besides checkins.
One that you can certainly do is to be one of the voices of positivity and gratitude.

If I enjoy or benefit from something someone has released into the world, I've started trying to send them an email of thanks.

Many times I've gotten responses back, and they are always really grateful for the support. As a hopeful creator with a small but growing following, I've gotten a few of these myself and they really are motivating.

I generally make it a point to never criticize anyone online, since they probably know everything they are doing wrong acutely well and don't need me to tell them again.
Hacker backdoors popular JavaScript library to steal Bitcoin funds
If you buy the printer that is "consumable" more than once, you deserve it :)
It's caveat emptor, even when you pay $0. When you choose an open source tool or library for your project, or even a closed source one, you need to evaluate what support / bug fixes / modifications / enhancements you will get in the future and if it will meet your needs. Are you prepared to fork or workaround things where it doesn't meet your needs. Or is it better to choose another library or tool?
Very weird that those were the last questions on the list...
This, and then make sure the rewards trickle down to everyone involved: https://github.com/ktorn/vdp
I would argue that if you release an open source project, you do have a responsibility to communicate enough about your intentions that potential users can base their expectations accordingly.

That doesn't have to be at any particular level. But if a project is unmaintained... why not tell people? If you are sharing a project in case it's useful to someone but don't really intend to deal with any external bug reports or feature requests at all... why not just clearly advertise that?
From my reading those phrases are actually attempts to use terms a lay person can understand i.e. the opposite of esoteric. "Holographic duality" is the only phrase that is legitimately esoteric, the rest is just baby talk.
I vividly remember a sense of total awe watching it, thinking here we are, watching a broadcast from inside the JPL - as it happens! - of a craft in a totally new, complex method of landing after travelling and being guided millions of kilometres.

What struck me in particular was the sense of wonder at being able to see that first image of the wheel - transmitted across the globe live as they received it.

Such a privilege and accomplishment.
Lately, I worked with a couple
of research groups conceptualizing practical ways to achieve DNA archiving. I think that DNA or molecular-based archiving will become a thing. DNA is really good as an archival medium.
This is an excellent depiction of the distinction between "free software" and "open source" as ideological frameworks. As licensing schemes, they're the same - but open source ends at the licensing scheme, as the author correctly points out. If you want to use it for a side project, great. If you want to use it to make money, great. If you want to use it to commoditize the operating system for your worldwide advertising infrastructure, great. If you want to embed it in your iOS app or in iOS itself (and the license permits doing so), great.

The free software movement, however, says things like this (from https://www.debian.org/social_contract ):

Our priorities are our users and free software.

We will be guided by the needs of our users and the free software community. We will place their interests first in our priorities.

We will give back to the free software community.

In other words, free software is about you.

I would quibble with the claim that the open-source process is what produced Clojure in the first place. The open source movement has benefited from sailing in the same direction as the free software movement and using the same tailwinds. Without the free software ethos (which was behind GNU as well as a lot of the Lisp work at MIT), would Clojure have been able to stand on the same shoulders, and would it have attracted the community of users and the ecosystem of libraries it has?
https://github.com/barrysteyn/node-scrypt/pull/119
This is why I've never worried about anyone stealing my ideas or code. The set of people who could both actually have the ability to pull off forking something and running the project, and have the motivation to see it through, is so vanishingly small as to be non-existent.
> I've never seen a start-up fail on account of technical debt.

That's because noone ever says "XYZ startup failed because their code quality wasn't good enough." It's usually something closer to "Their customers didn't renew contracts, they had to slash headcount, and went into a death spiral from there."

If you press for details, the deeper reason might be "they couldn't turn around features fast enough" or "the app was slow or their servers went down too much" which is a symptom of too much technical debt (either directly, or because the better engineers on the team choose to leave as a consequence of the technical debt).

I agree that early startups don't fail because of technical debt, but I'd bet that many mid-size startups do fail because of it.
There are lots roads with the same environment or with environments less likely to lead to collisions with cars, bicycles, and pedestrians that nevertheless get lower speed limits.
> Facebook forked PHP to make Hack to try and make PHP usable.

Facebook clearly found PHP usable before they created Hack, otherwise they would (a) not have bothered and (b) may well not have existed in the first place.

The accurate statement is probably closer to "FB created hack to adapt to performance demands at an unusual scale and add some additional typing discipline bringing additional order across a large engineering team."
Elon Musk: You Can Only Change the World Working 80+ Hours a Week
"Sell" is a pretty important word there. There are laws and regulations for those, and neither comes with an explicit license saying something like "disclaims all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose."
I was basically assuming you're ahead of the game, since your paperwork must be in at March to be on-time, unless you file for yourself or if your accountant really likes you, I guess... you're right, the deadline is in April, and I assume similarly, charitably, that taxes paid in May as I said are mostly on-time, while that's not strictly true.

YMMV IANAL this is not legal advice, if your tax budget is not already ready to be paid off in March, then I wish good luck to you.
FP and OOP are orthogonal... You can have purely functional objects
Exactly, actually. My point being that swiping my fingerprints is a big enough pain in the butt for relatively low value of return, and it doesn't scale across users.
I've always suggested people find one that works for them. My father in law loves competition and numbers, so Weight Watchers lets him accumulate points. My wife hates cheat days and they don't really have the intended effect on her. She's also fine eating the same thing almost every day. A lot of the fad diets are fairly similar in that they're low-carb and reduce sugar; Atkins, South Beach, Keto, Whole30.
New Coub Video Mixtage:174 – New Vines Set (Videos FunnY Cube)
I believe Charles Stross described it as 'Whither bohemia in a hyperconnected world?'

Guy's got a way with words...
And the moral of the story is … ?
This is true. But HHVM lit a fire under the php devs to get php7 out the door with significant performance improvements. (php6 never saw the light of day). Php has improved so much with the 7x releases.
The Perils of Liberal Philanthropy
Yes, it sucks. But I suspect that his reticence about hanging out had more to do with the pain than the opioid addiction. In my experience, opioid addicts can be quite social. At least, when they're not nodding out or in withdrawal. I don't like them much as friends, however, because you'll likely never matter more to them than avoiding withdrawal. Same with alcoholics and other addicts.
“You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”
"Tech companies pay poor Kenyans to produce training data for AI"
https://news.ycombinator.com/item?id=18369384
Noooooooo. All of these metrics are a mistake, don't measure any of them. Measure the things that actually matter about your product and whether or not it's getting better or worse.

Measure outcomes. Only outcomes. Try and make sure your metrics capture the real outcomes and not just what you see in a lab. This usually means you need to use field data to get that information.
I don't like unnecessary layers. Interpreted languages waste silicon and energy. I've heard startups justify using Ruby or PHP by saying "servers are cheap", which is just a bad engineering mindset.

Instead of building PHP apps on a PHP platform built in Go, people should just build apps in Go. Or in C++, D, Nim, F#, C#, or even Java 8 or 10 with that new AOT compiler. (I think F# and C# can also be compiled in advance with CoreRT, but even if they can't, they're a huge upgrade over any interpreted language.)

I would mention Rust except that it's terrible. All popular programming languages in our timeline are bad, and deter millions of smart people from the profession. But Rust is extraordinarily bad and should be replaced.
I tried this when I was 12 or 13... from textfiles.com.
if you able to differentiate this is bad from good, that by itself is a progress :)