skysight-inc/HackerNews huggingface dataset:
Statement Regarding Moq – .NET Foundation
In ideal world it would not matter, but business and politics are intermixed more or less pretty much everywhere. Unfortunatelly, countries like Russia or China
have much more politics influence. Hence, I try to avoid them.
Good point : maybe that's why there was no mention of Scala at the time.
https://en.wikipedia.org/wiki/Benevolent_dictator_for_life has a list of BDFLs. Bram is the first BDFL in that list who has passed away. We're in for a generational shift the coming decade(s). It makes sense to prepare - that is how you preserve a legacy, and the community.

I've been impressed with how Bram's passing has been handled by his family and friends with respect to his legacy and the future of vim.
> It sounds like badly documented code then. A function, especially if some kind of API boundary, should absolutely state whether it can or can’t return null.

Of course, in the type system.

Just like we're "documenting" types themselves in the type system and not in JavaDocs.
https://www.youtube.com/watch?v=pZwvrxVavnQn [2:49]

I agree it's not an absolute, immutable concept, but I think it's a hell of a lot clearer than "good" or "right" or "fair". What makes consent is the fact that either party can opt out at any time for any/no reason. It's consensual because we are decision-making agents, and in spite of privation we can still choose to refuse to transact. Consent is violated by force or direct threat of force, not by the circumstances the transacting parties may find themselves in.

If you're very horny can you still refuse to consent to sex? If you happen to be dying of thirst and I offer you a glass of water, can you refuse? You can. Are there may reasons why you would? I don't imagine so. Does it follow there there are no circumstances under which anyone would refuse? It does not.
It does guarantee transition to a free as in freedom open source license after a set period. Seems to be (at most?) 4 years.
If I have to pay developers, operate a business, allocate time and money to create value and take the risk that comes with it, and you come and take my work unchanged, strip all atribution and mereley resell it, then I can't succeed by definition. The most talented businessman on earth cannot.

If that's what you think open source is, it'll vanish. No commercial system can exist like that and it should not because it effectively means distributing resources from people who do everything to people who do nothing.
> making them much more maneuverable, which is the most important factor in a dogfight

as an example problem in statistics class in grad school, we showed that the intuition that maneuverability is most important in a dogfight is incorrect, that it's speed (fly in, take a few shots, zoom away, lather rinse repeat) and that's why WWII fighters were so designed

of course, all else being equal, maneuverability is good, but all else is not equal, there are aerodynamic tradeoffs
I submitted via Github 2 days ago [1] but didn't get any traction. But probably couldn't be submitted again with the Github link...

Anyways nice to see some discussion here, didn't read a lot elsewhere about the project.

[1] https://news.ycombinator.com/item?id=37053201
How is this still a thing? Absolutely nuts. What happened to the www.
It's very hard to take you seriously if your argument is "just read the code you call to figure out if it returns null or not". That just isn't feasible in large code bases.
I'm just surprised that this hasn't become a big issue for Amazon. Is it that most people aren't aware? Isn't it a big enough story for some news outlet to investigate and report? If it became generally known that a large % of products on amazon are fakes, surely it would affect sales.
If they're so bad, then why do so many people have them, and seem to be able to cook good food on them?

I appreciate that there are better stoves out there that might make certain things easier but the stove is not the thing that's holding back my cooking.
Yup this is how I see things evolving too. It’s a long game though and I suspect there will be a few twists yet to come.
Almost. When Musk was fired from PayPal, it wasn't called PayPal yet. It was called X.com. PayPal was a competing company started by Theil.

The two companies merged, and a lot of discontent came about in that process, leading to Musk being kicked out.

Musk says it was because he was too insistent that the new company should be called X rather than PayPal, but everyone else says that it was because Musk was incompetent and that incompetence was hurting the company.

I don't claim to know who's closer to correct, but the ouster was brutal and each party had lots of vitriol to spew about the other.
Vim has had a legitimate impact on my life. Over the past 15 years I've been using it, "set -o vi" and similar in psql/ipython get added into my rc files almost immediately on a new host. Many, many hours upon hours of living in a shell have been made so much more enjoyable because of his work.

Thank you for posting this. Rest in peace, friend.
I didn't see much in the way of details on the Anker site regarding their system. It seems none of the companies selling their systems make it as easy as tesla to order one.
I know, but why it is necessary?
I think the real question is whether the benefit is worth the 10%. That's pretty expensive.

From a macchiavellian perspective, it does appear that the benefits mostly attach to the founders (unless you are selling products to startups) and the 10% attaches to the company, which suggests that the optimal strategy post-YC may be to fail and start another company.

Edit - Obviously I'm not suggesting killing a good company that hits it big and gets a bunch of traction, but if your post-YC company isn't in that position (and almost all of them aren't, by the way, thanks to the risky nature of startups), you have some very awkward math to do on whether to pivot or shut down.
This will be a significant boost to London, already home to vast amounts of money laundering via real estate, all facilitated by well established networks involving thousands of middle class professionals and the UK's crown dependencies with convenient secrecy laws, nominee directors etc. to conceal beneficial ownership. 70% of the apartments in most premium developments are owned offshore, many with concealed ownership -- 11% of all of the properties in Westminster alone.

I recommend the following books by Oliver Bullough:

Moneyland https://www.amazon.co.uk/Moneyland-Thieves-Crooks-Rule-World...

Butler to the World https://www.amazon.co.uk/Butler-World-Britain-Empire-Found-e...

and, by Tom Burgis

Kleptopia https://www.amazon.co.uk/Kleptopia-Dirty-Money-Conquering-Wo...

and this YouTube video

https://www.youtube.com/watch?v=4n3txSCoKn0
People are always terrified of these microbes that are millions or billions of years out of context.

It's like being scared that a trout is going to beat you in a foot race, when you're racing tigers every day.

The things to be scared of aren't those that haven't ever seen you before. It's the ones that have spent every second of every day, for hundreds/thousands/millions of years perfecting their ability to eat you that you should worry about.
Archive.li now requires goggle JavaScript?
Originally https://archive.li/ was able to be accessed with cookies and javascript disabled.

Now it seems to require a capcha that requires cookies and javascript from goggle be enabled.

Anyone find a workaround?
Although, thinking about it now, the letters do come after each other in the alpbabeth except that the I is missing between the H and J, but maybe they did that intentionally because it can be confused with the lower case L. So maybe just coincidence after all, but still it was special for me. I never saw this at the trains and now suddenly the week after Bram passed away this shows up.
Poorly worded, perhaps, but it is a real problem. Around here, landfills that have been around forever are either now full, or nearly full, and nobody wants to allow new ones to be established.

As such, throwing things away municipally has become increasing difficult. When I was young you could throw anything you wanted away to your heart's content. Eventually a cost was attached to the volume being discarded. Recently, now, there is a limit to how much you can get rid of each week.

There are solutions when you have more, like employing the services of outside disposal companies, but I can see how that quickly becomes a "I'll contact them later when I have time" and soon the things are piling up and it is not long before you have a daunting task on your hands that you don’t want to touch.
I wouldn't call them a competitor by any stretch; more like a partner. A Terragrunt codebase just wraps Terraform, with the same exact backends (including Hashicorp's SaaS offerings) and the same exact providers and everything.
This rings true for my own experience.

While I have avoided most of the counterfeit dupes (of which I will broaden beyond just selling clones; there are plenty of shady products with questionable descriptions that don't match reality), they have been steadily increasing prices on many products to the point that I am often better off driving to a Lowes or Home Depot for faster service and better deals on things. I also can't emphasize enough that they haven't been that competitive in the laptop market or the home desktop PC market either for years now. Parts and DIY, sure, but I frequently find better deals elsewhere on what is usually the same hardware. I suspect the suppliers are the real root cause of this, but either way it ends up a bad deal. Additionally, finding things with targeted specs is surprisingly difficult at times, and can easily lead to choices that aren't even correct when search starts looking at adjacent products.
It's often also impossible to get after-sales support for many of these mystery "brands" and they don't tend to stay around for long before they change names again. I am sure this is by design.
> Inevitable end for every open source company since the free money ended.

Yeah. It seems like the Apache/MIT route has been working “well” to support a suite of libraries. But for bigger “business-critical” full-on products, like databases etc, you see much more weird contortions, including making self-hosting difficult and feature-gating essentials. Better than closed source, but not ideal. I’ve been thinking for a while that licensing is likely the pragmatic way out. But it’s important that it’s broadly understood, fair and clear.

> […] a product or service provided to users or customers outside of your organization that has significant overlap

Ouch, judging by the language it seems like it’s (1) unclear and (2) the authority on that ambiguity leans in favor of the company, which paves the way for selective enforcement. “Don’t worry, we aren’t going to come after anyone” is not convincing when legal documents are being signed. Hoarding soft- or future powers is a huge red flag in contracts, imo.

What do others think about this license in particular?
Show HN: Fully isolated honeypot SSH server using thrussh
Ads and donations(mainly), just like other open source project operates

operation cost can be managed, but the cost for getting people to the platform might be an issue, have to figure out
It's suggestive of p-hacking. "Look, the bottom of the interval is just above 1! Finally I can publish this."
For what it's worth, I also missed it the first time around. It's worded a little strangely if you're going through them quickly.
Reminds me of the rumor that the reason it went "Windows 7", "8", "10" and skipped "9" is because the fear of a codebase that went:

if(version.StartsWith(“Windows 9”)) {
/* 95 and 98 */
...
}
Sure, I'll take a swing!

If we define "knowing" some fact F as "we have proven that F follows from prerequisite facts A1..AN", then we can imagine all knowledge forms a graph where prerequsities point to the facts that they prove. Either this graph is cyclic, or there are nodes with no inbound edges. Therefore, there are facts which are either non-demonstrable, or only demonstrable via cyclic logic.

I think this works, unless of course you have another definiton of "knowing" :)
If you want people/companies to contribute back, why volunteer your code under a license that doesn't require that?
> Granted, my experience with DEB has mostly been limited to Ubuntu - so it could be that/Canonical.

It is not a Canonical specificity, but it is overridable behavior.

For the dpkg prompting on configuration file changes:

https://raphaelhertzog.com/2010/09/21/debian-conffile-config...

> You can also make those options permanent by creating /etc/apt/apt.conf.d/local:

> Dpkg::Options {
> "--force-confdef";
> "--force-confold";
> }

Along with invoking apt with -y (assume yes) will get you close to the behavior you seek. Or as a permanent setting:

APT::Get::Assume-Yes "true";
> Musk says it was because he was too insistent that the new company should be called X rather than PayPal, but everyone else says that it was because Musk was incompetent

I feel like one of those is an example of the other :)
Interestingly, the principle of single responsibility is specifically why I like GraphQL over REST. As your frontend complexity grows, your REST payloads tend to become carefully-balanced collections of complex shapes, and it becomes very difficult to maintain and refactor over time. In GQL, by comparison, each field or mutation has its own isolated implementation, authorization is handled at a granular level, and frontend queries can evolve as needed without imposing any significant need for changes on the backend.

REST is great for small, compact APIs which serve a couple of views, but as the product grows in scope and complexity, GraphQL ends up feeling significantly easier to keep straight.

The other thing is that it's very easy to build "complex" REST APIs on top of GraphQL - execute an internal query, reshape the result into a JSON payload to conform to the REST contract - but implementing GraphQL on top of a bunch of REST calls is a lot hairier. GraphQL feels more like a set of primitives, while REST is a coalesced interface.
Rule #1: stay on the boat
Testing Intel’s Arc A770 GPU for Deep Learning (Part 1 of 3)
regarding Mr. Cave's critique:

From Alan Turing's paper, "COMPUTING MACHINERY AND INTELLIGENCE"[0]

"(1) The Theological Objection
Thinking is a function of man's immortal soul. God has given an immortal soul to every man and woman, but not to any other animal or to machines. Hence no animal or machine can think."

regarding your comment:

If you haven't watched The Beatles: Get Back[1], I highly recommend it, if only to watch the Fab Four brainstorm lyrics.

[0]https://redirect.cs.umbc.edu/courses/471/papers/turing.pdf
[1]https://www.thebeatles.com/beatles-get-back-disney-original-...
> I'm sure they took all the needed safety precautions

no they didn't, one of the most prominent advocates working on this problem was killed by a ricochet. let me see if I can find it...
GPLs are a bit complicated for companies because (personal opinion alert) I THINK it is ok if you’re a company, member of a particular community, to be able to embed that on some product and not be mandated to open-source the whole thing.

IMHO not everything needs to be open-source, but in many case it just makes so much sense that is a dumb idea to reinvent the wheel.

Many projects are succesfull this way. One I can think of is LLVM.
I grew up in a community like this, in a family operating on your set of assumptions.

The problem isn't losing half the value of your property. The problem is that after 20 years, moving on isn't as easy as it sounds. More importantly, selling at any price is way more difficult that it sounds. If you don't GTFO early enough, the muni has lost a ton of revenue without right-sizing so the remaining owners on are on the hook for huge property taxes just to service the debt (further suppressing demand at literally any price).

And there are all sorts of reasons you might not GTFO in time. Just two more years until the first kid is done with HS. And now just two more years for the next kid; still seems unfair to move them. And so on. And then just 2 more years until you've saved up enough for that dream place in the mountains. And then it's too late.

So you are stuck with this albatross that you literally cannot sell. Property values, even at $1, are totally hypothetical. There is no buy side of the market. At all. Enjoy your property taxes, or figuring out how to abandon the property.

It's the suburban muni equivalent of a condo unit that is attractively priced but won't ever move because a contingent of geriatric owners have managed to run up $2k/mo HOA fees by unwittingly turning the condo association into an assisted living facility (but not making it far enough to actually be an assisted living facility).
Interesting observation. I recently watched a documentary about Compaq, and this saga reminds me of a previous time when IBM tried to put the genie back in the bottle with MicroChannel architecture. Let’s see if they fare any better this time
I recommend disassembling hard disks and keeping the magnets, they're super useful to have to capture loose screws and the like. Glue one to the end of a stick or telescoping pointer and you have a way to retrieve magnetic things that fall behind furniture.

You could also literally wipe your data by using a little sandpaper on the platters if you really wanted to.
That is entirely dependent on how much you're leaving on the table by failing. When gambling, it might make sense to quit while you're up but that entirely depends on the expected value of your next bet.

From a macchiavellian perspective, you also have to consider how much benefit the founder would stand again from having a more successful startup instead of failing.
>Employees have realised we are equally as effective working from home and simply do not want to waste 2+ UNPAID hours of every day travelling to a corporate building for the sake of it.

Most were effectively fools to not realize that before Covid. Now when will they start realizing that out of the 5 days that they work in a week they are working without compensation anywhere from 2 to 4 days effectively for the Govt/corporate/overlords because of taxation at various levels. ( taxesincome/property/sales, inflation etc.)

To summarize the meta problem is the minions, not the corporations. In this day of automation most people should be having a lot of free time and relatively little work, but here were are in the year 2023 working and commuting our asses off.
a cointoss
We actually pivoted multiple times:

1. We applied to YC and initially started work on what we referred to as "data-stack-as-a-service". The premise was to provision, configure, and maintain the different components required for a data stack: Data Warehouse, Integrations, Transformations, Visualizations, etc. We had a working product and a few paying customers. Ultimately we decided to pivot as we felt the market for this was only small companies with small budgets (many of whom might not even need a mature data stack).

2. Then we released a small open-source tool for Postgres that could easily send webhook notifications when data was changed (pg triggers sent websocket messages to a Go application). Off of this we dove deeper into database tooling and building a platform that offered branching, change management, and other modern features for Postgres. We also had a prototype and slightly larger contracts with a few early customers here. We decided to pivot from this for a few reasons, but ultimately we lost conviction in the idea and were more excited about data import challenges that came up during user interviews.

3. As you mentioned, we're now working on CSV import as a service. After building and maintaining CSV import tools many times ourselves, we believe there's an opportunity to provide a robust, pre-built experience. There are actually a few other products in the market today. Our initial focus is to be the most developer-friendly choice (a big part of why we're open source). We want the decision to leverage an existing service to be a no-brainer for any engineering team tasked with supporting CSV import.
A Detailed Look at the Outcomes of Minneapolis’ Housing Reforms
Only someone who does not understand what the Karman Line is and is not would claim that there is "a definition for space" like kg or m.

If you are now going to resort to "the FAI's definition", by the FAI's standards Yuri Gagarin did not fly the first orbital flight because he ejected from Soyuz I near the end, something the USSR kept secret so it could claim the achievement.
> on all future releases of HashiCorp products

Anything before the change is still MPL and can be forked and built on top of freely.
Can you find a new job the very next day? Can everyone? Why not at least have a few weeks, what's the harm in that?
Not all that curious... https://flatfile.com

If you're building a vertical SaaS and want to support import from a file, and don't want to spend time reinventing the wheel, this could be a big win. This would let new users bring in existing data from another SaaS (that supports CSV export) or where the incumbent is likely to be Excel. The development time it would take to make something like this solid, usable, and flexible enough to handle different formats would, in most cases, be better spent on building domain-specific functionality.
Similarly, when drafting some sort of communication (email, documentation, etc.) one might have a URL as the last "word" of a sentence (or comma-delimited clause, etc.) and apply typical rules of grammar that say not to use a space between the last "word" and the subsequent punctuation. Then upon saving (or upon viewing, or sometimes upon hitting the space bar, depending on implementation) the automatic linkification kicks in, and in my experience enough of them aggressively trim such punctuation (period, comma, etc.) before setting the href that people can get away without thinking about this, but some linkification functions end up keeping it, yielding a 404 error when clicked. High-usage products like email clients and chat apps tend to aggressively trim, while lower quality products like ticketing systems tend not to, as far as I can tell.
It's just a matter of time. They're Apache 2.0 for now. But they can pull out at any moment just like Hashicorp, Grafana, Mongo any many others..
A Living History of the Humble Paper Airplane
Beets. If it had been Beats, it would have gotten more attention :-)
Source-available is still hugely beneficial to users, even if it’s not open source.