skysight-inc/HackerNews huggingface dataset:
>It is not nonsense. Microsoft testified against the man in court. They wanted him to go to prison.

He was selling counterfeit disks as genuine. Was warned to stop, and didn't. You either haven't bothered to read the link provided, any of the court rulings (it was upheld on appeal), or you're just such an MS hater you're going to deny reality.

Either way, when there are literally email threads of him trying to sell disks to computer refurbishers as "genuine" and being called out for them being counterfeit, you're not going to convince me he was the innocent victim he's claiming to be.

I'm just going to assume I'm correct in you not reading any of the links provided, and I'll leave this here:
https://blogs.microsoft.com/uploads/prod/sites/5/2018/04/Ema...

And if you want to "prove" that MS is in the wrong, I'd suggest you link to a lawyer disputing the results of the case. Not a guy who fixes laptops for a living.
unemployment, or lack of spending power due to underemployment?

I think you misunderstood. You are describing negative societal value. Long-term unemployment can ruin not only your life but the lives of your family members.

Econ 201's solution is to punt on the issue and start doing calculus, because the economics orthodoxy was developed by heartless market neoliberals and computer scientists, and they can't really rationalize it in human terms. You literally have to go to grad school to un-learn all this shit.
Eh? Chen Shuibian did declare independence, like 10 times
If Sears sold some assets to Lampert's holding company for less than they were worth, there are probably laws against that (though proving it in court may be a different matter). But if Lampert's holding company was the high bidder, why shouldn't they buy the assets?
> It's not always possible to change the data structure -- different ways of modeling data have different trade-offs.

I agree with "different ways of modeling data have different trade-offs", but I don't understand how that leads to "it's not always possible to change the data structure". I revisit trade-offs all the time.

Could you explain? I might need a concrete example.

> Also, it could be something like structure coming from a 3rd-party crate using borrowing and you want to stick it into "Arc" of some sort. Or put it (with the thing it borrows from) into a lifetime-less struct, so you don't have to care about these lifetimes.

Yeah, certainly the refactoring becomes harder (maybe implausible to do automatically) when you can't change both sides in one PR, and when you have to convince someone else to change their interface / bump the major version. It still can be done (partially?) by hand at least; it's just a matter of cost/benefit.
No. In this case that part of the analogy is actually not apt at all. To use another bad analogy I think my point is that the feeling awkwardness actually comes from the fact that I was doing the equivalent of holding the hammer by the head and trying to pound nails, only to later realize that I should have been holding the handle, and that there actually was a handle. In python it is like having a sledge hammer that you can't possibly hold by the head, but that no matter how hard you try you keep putting holes in the wall when you try to hang a picture.

Someone will say 'but why not use the tack hammer?' and, at that point I argue, I am no longer using python the language, but a whole new language that happens to look like python but that has a different runtime and a different set of assumptions. This even happens inside of the core language where `[d(a) for a in b if a == c]` can be valid in some scopes but not in others. The other language does the opposite, it says "you can't do that" and so I try to hold the hammer by its head and think that it is the language that is awkward because I don't know how to use it and that there is an fact a nail gun that is configurable along every dimension from nail diameter, to nail length, to insertion speed and pressure profile over the whole insertion timecourse, it is just not there in plain sight and I the first few times I used it I accidentally nailed my feet to the ground with railroad spikes.

I guess it is more that every time I learn more about python it is about what I have to NOT do in order to be safe. In the other case I learn what TO do in order to solve the problem the way I want to. Maybe the clearest example I can think of is lambda, where you have something that looks like a lambda, but that doesn't doesn't even work like the def (): that it copies due to the biases of the language designer. Honestly it would be better if Python just removed all the syntactic features that don't have generalized runtime support because that way you don't have to know which features you can use where. Sure, there is a use case for lambda in certain contexts, but if Python refuses to support lambda as a general abstraction that I can use everywhere, then it should be removed from the language, because including it leads to those hidden inconsistencies which require an enormous memory burden on the developer just to know what is not allowed. That is dead knowledge that in no way empowers and enriches the programming experience.

In essence the push for pythonic code is not just about maintainable code, it is about keeping people on the happy path without removing delimited abstractions, which is fine, except that the explicit solution to this problem would be to have `from __i_know_what_im_doing__ import lambda, comprehensions` so that the core language didn't misleadingly offer these delimited abstractions. Of course this means that many of my favourite features would be thrown out until some core technical challenges were resolved.
If we ever do solve the last mile, it would probably be one of the less interesting consequences, as it would probably imply we've built an algorithm capable of learning and thinking to a similar degree of a human.

To that, though, I'm definitely not holding my breath :)
What does your comment say when translated to the language of mere mortals? Asking for a friend
Why All Programmers Are Creatives
No longer? Read some history, start with yellow journalism and muckraking.

Learning history will teach you more about things today than any news source.
We can't manage it until we remove employment as the sole condition for access to basic services like healthcare. We also need to ensure that people are able to retrain themselves if/when their job becomes obsolete.
Previous poster claimed that all of the magic was hardware but I've always been told that it was in the software. HPE now seems to have some agreement with Arista.
Ask HN: Why recent post “What do you hate most about HN?” downvoted to oblivion?
Referring to https://news.ycombinator.com/item?id=18184725

Was it because word 'hate' is too strong for HN to take? I thought HN is quite a mature community to take these kind of questions. It could've seen as a way of improving itself, but instead it's moved out of HN/Ask HN home page quickly, didn't even stay 9 hrs in 'Ask HN' page when posts older than 2 days are still floating.
Etsy’s experiment with immutable documentation
Not piracy, but the revenue the studios get out of Youtube would seem way less than what they'd get out of a paid platform, so they're still loosing out compared to just licensing the content to all paid platforms.
Cool, an english-major type essay about how the web sucks now. But what does this do to fix the web?
I thought Kenton Varda was the author of protobufs?
To be fair, this original draft ordinance was FOIA'd. Our Ordinance Revisions Committee looked at it at a recent meeting and made some substantive changes. Then our awesome Planning Commission looked over it last night and, with the input of our City Planner, had some really good discussion about things like the number of food trucks you can have per number of parking spaces as well as discussing interactions with residential and mixed-use zones.

The Planning Office also released a map of the updated zones allowed under the ordinance, which, if you ignore setbacks, should include every parcel that isn't straight residential. I believe it was our City Planner who mentioned that someone had FOIA'd the updated map about 20 minutes before the Planning Commission meeting. I only wish I could've mapped it sooner! ;)
The people going in through tunnels are going for work not to have babies.

I guess it’s much easier to come into México in a ship first and then cross into the US

Birth tourism is done via airports and turist visas
I've wanted NaN and Infinity on a few serialization worlds. Mainly because I didn't want to have to reinvent what the IEEE numbers already have.

My complaint on the items being less than compelling is that they almost instantly devolve into bitter fights about what I'm supposed to care about. I fully grant that XML was too heavy in much of its schema attempts. However, it is much easier to reason about the extremity of XML than it is where in the middle road I want to be in.

That it is an evolving document being developed in the open is worthless if it is not always maintaining backwards compatibility. And, since there is no way to maintain backwards compatibility now that that ship has sailed, I'm skeptical of it.

I'm sure it will hit a good maxima at some point. But "is pretty easy to read and works pretty well for validation" was also fairly accurate for most XSD work. "People are already being very productive with it" was absolutely accurate. It was only when people started to stretch with it, that things got obnoxious. And we fell back on JSON not because it was somehow technically superior, but because it was technically easier.
what are your policies regarding potential archaeological sites that may exist in the bounds of the commune?
Protobuffers always seemed like an interesting approach but every time I've tried to use in a prototype I've ended up deciding against the added overhead of including them. And then I use JSON because I simply wanted versioned serialisation when messaging or persisting data.
Two problems with title of post:

- 2017 article

- Ecole 42 is not a "university":
https://ahdictionary.com/word/search.html?q=university
Hmmm... delicious bitmasking. That's when you know the author is serious about squeezing performance out of a JS VM: forcing 32 bit integer optimizations.
Bandcamp in my mind is just about the only company in this space I want to buy things from (including Spotify, Youtube Red, Amazon Music, whatever else). It:

- supports the artists (and lots of them, not just the biggest ones)

- gives me instant, irrefutable ownership of the music I've bought

- gives great download format choice

If an artist is on bandcamp, it is a no-brainer for me to throw them their minimum + 1/2 dollars and buy an album. I can't say everyone thinks this way, but the feeling that I'm supporting the artists is felt more directly than on any other platform, and it feels good. To me, it's worth the price increase from free (to a point).

If I could buy all my music on bandcamp I would. The only thing better than bandcamp would be a distributed/federated network of direct-from-band merch and album stores with (somehow) good discovery features written in a way that made it easy for bands to set up payment distribution (ex. stripe integration, shipping fulfillment integration, etc) -- but bandcamp is close enough.
That doesn't seem like the author's main argument - they say: "Protobuffers were obviously built by amateurs because they offer bad solutions to widely-known and already-solved problems."
I only interned at Google but I also really liked protocol buffers, somehow it seems very structured and defined to me, and better than Java. But this could just be that I haven't worked with better things... Lol
That really depends on the nature of your data. The space saving in protobufs really comes from its variable-length zig-zag encoding of numeric fields (including lengths for arrays and strings).

Tbh, i'm surprised msgpack didn't produce smaller outputs for you, because it really should (at the cost of being slower)
Protobuf did not support maps for a long time. In practice using a list of key/value pairs works fine for most use cases. Sending the message over the wire is obviously always O(n); if you need fast inserts/lookups in code, then it usually makes sense to convert to and from the appropriate in-memory data structure for that purpose.

That said, I think maps are a fine feature for a serialization format to have. But, I haven't gotten around to adding them in Cap'n Proto because I have yet to hit a use case where I wasn't happy with a list of key/value pairs.
The Planning Commission had a working session last night where they discussed lots of these issues, including ice cream trucks (everyone was very concerned about accidentally banning ice cream trucks heh). I forget what the conclusion was, but our City Planer mentioned that ice cream trucks operate in a public right-of-way (the road) and aren't parked on private property to serve food. I think they're going to revise the ordinance for clarity, though, because an ice cream truck and a food truck serve different purposes, I'd argue.
They don't run forensics on the actual device if at all possible, only a read-only cloned image.
This is a well-known phenomenon in political science---Mancur Olson, "The Logic of Collective Action," is the relevant read: small groups that can generate group-specific benefits (like suppressing competition for their businesses) have a much easier time carrying out organized political activity of all kinds rather than large diffuse groups trying to create public benefits (like food truck availability)
Do web assembly files really have a .wat extension? This can't not be an easter egg reference to the famous talk, right? :)
Majority of energy consumption and population happens in cities / industry, so if we are talking significant co2 soonest, we should really focus on these.

For large consumers like these to go solar/wind, you will have to really over-provision solar/wind so that minimum possible power output is still enough. (Calm night, anyone?) This looks highly inefficient and tough to predict.

Whereas nuclear can and are already operating in load following mode routinely: [1]

[1] http://www.oecd-nea.org/nea-news/2011/29-2/nea-news-29-2-loa...
No, the author is showing off how smart they are, and in an unprofessional and nasty manner to boot.

It's kind of you to gift the article with some genuinely thoughtful conclusions, but you're doing all the work there, not the original.

As the grandparent says, it's easy to poke holes in something, especially when disregarding important requirements that influenced its design. The fact that the OP can't point to any implementation of the "right" way to do things is telling.
If protobuffers are wrong, then I don’t want to be right.
Prepaid SIM card?
The term of art here is "Hispanic white" vs. "non-Hispanic white".
Let a thousand flowers bloom and all that, but come on. That particular flower is a freaking baobab already. I assume it's mostly for use outside of browsers.
Apple, Google execs named to Saudi Neom advisory board
Thanks, I appreciate it! I've never been HN famous. Ann Arbor has a vibrant tech scene and a responsive local government, which makes it a fantastic environment to use technical skills to get involved, I think. I already have a few ideas about what to do next (I know at least one person who was interested in seeing a heat map of building permit issuance, which would be pretty cool).
This article seems to make the argument:

Premise 1: There's this big problem of inequality

Premise 2: UBI is not a perfect solution for solving this inequality

Therefore, probably,

Conclusion: We should reject this solution

This is called Nirvana fallacy [0], also known as the perfect solution fallacy. For example: "Seat belts are a bad idea. People are still going to die in car crashes."

[0]: https://www.wikiwand.com/en/Nirvana_fallacy
1) If cooked food comes in contact with a surface that raw meat was prepped on, the cooked food can become tainted.

2) Most cities fire code say that your backyard grill is required to be a certain distance from the building structure (my local ordinance says 15ft), it just so happens that most people ignore the local ordinances. Those codes are b/c of grill fires.
To note, there are more women than men in high school teaching positions, so what you're seeing might not be that STEM has a bias against women but that teaching has a bias for women (or any other out of a very big set of possible conclusions)

see: https://stats.oecd.org/Index.aspx?DataSetCode=EAG_PERS_SHARE...
The wording was pointlessly presumptive. Many HN users likely hate nothing about it -- hence they're still using it.

A better formulation would've been something like, "What one change would improve HN most?"

But even then, the topic has been beaten to death. If you don't like HN, it's easy to access the data to create your own UI. Many others have already.
Why? The whole fab becomes 2.5x slower?
Wikichip:

https://en.wikichip.org/wiki/7_nm_lithography_process
Proto doesn't really have a schema. You can encode a proto of type X and tell your program to decode it as type Y, and it might work. Might not, but might. You can easily imagine messages that are isomorphic on the wire. E.g.

message X { optional string foo = 1; }
message Y { optional X foo = 1; }

Encoded buffers of X will decode as Y just fine.
The same dynamic that results in zoning that prohibits food trucks also results in large swathes of residential area in suburbs with no real restaurant options inside walking distance.
Building a forward chaining rule in Prolog is trivial. Here's an example in 25 lines

https://www.cse.unsw.edu.au/~billw/cs9414/notes/kr/rules/for...

Allows for rules such as

iF
problem_in_kitchen and no_water_from_outside
then
leak_in_kitchen.
I love how sure everyone was that it's EMI.

Now I'm thinking of some crazy scenario where someone saves the day by putting an iPhone in a helium balloon to reversibly disable it.
BadBIOS wasn’t real? It sounded so innovative! My day is ruined and my disappointment is immeasurable.
No, you're right. The canonical way to store a map in capnp is to use a List<Pair<key, value>>. Personally it doesn't bother me that much (mostly from an aesthetic standpoint) because it is not meant as an in-memory, working data structure.

What does bother me is that in the above generic type, "key" and "value" must be pointer types (i.e. non-scalar). The reasons are not unreasonable but it's definitely obnoxious in practice.
> The assertion that funding levels might be positively correlated with (unmeasurable -- you've conceded this point!) true outcomes is not unreasonable.

No it's not unreasonable, as a hypothesis. But if you wanted to, you know, test that hypothesis, guess what you'd need: performance measurement. Which means that the only way you can prove that spending matters is by measuring its impact on performance, which is already being measured by the other variables. So, there is zero reason to believe that incorporating spending as an additional variable can improve your assessment of quality.
What I was reading? It is easy to badmouth someone without knowing the context. It is not uncommon to end up with a flawed design if you find yourself in circumstances like short deadline, uncertain requirements, lack of resources, small user base, no QA and so on that are outside of the developer means to change.
Once I was faced with a task of serializing object hierarchy to a binary on disk[1], with the requirement of transparent backward compatibility (and desired forward compatibility), and the ability to be accessed from several programming languages in the future.

Protobufs looked promising because of their forward compatibility promise, but it looked like they only work if you write your code from the get-go using them. Rewiring a 15-year-old codebase would be a nightmare, so that was not an option.

Boost::serialization[2] looked promising, because it's non-intrusive -- but even "dumb" forward compatibility (skipping unknown fields) is not supported -- and reading its archives from other languages seems nontrivial.

So I went ahead and rolled out a custom framework with C++ template trickery which was non-intrusive, wrote to SQLite (with a fixed ORM schema), and did the job.

I wondered for a while if I was re-inventing the wheel, but in the end, I am glad I did it:

1. It wasn't that much work - especially compared to rewiring everything for Protobufs

2. It made me appreciate the goals and the API of Boost::serialization better - mine ended up being not too dissimilar. It was a great way to learn that - or any other- serialization API - without even looking at it! Now it's "let's see how they did ___" instead of "what does it do and why is this here".

Reading this article made me glad again: partly, for not depending on Protobuf -- and partly, for it having some of the same design flaws that I have (like having difficulty telling a zero-initialized value from a value not present in the data).

But the take-away for me was that sometimes, writing a custom framework is justified. Not all tools are suited for all purposes. Figuring out what one wants, and checking the list against the goals of a project can save a lot of headache.

[1] Binary was a necessity because some of the data is large arrays of full-precision floating point numbers, on the scale of 10-100MB. This was scientific data, no precision loss on saving/loading was acceptable.

[2]https://www.boost.org/doc/libs/1_67_0/libs/serialization/doc...
- cycle to work, work from home, car pool in a plugin hybrid/electric car

- improve the energy efficiency of your house (aircon, heating)

- eat less beef

- invest in solar panel/sun thermal collectors

- pick train instead of a car for a trip

- reduce waste and buying unnecessary stuff

- Lobby for certain regulations like more charging stations for electric cars, more bike lanes, electric cars to use a bus lane, property tax that takes home energy efficiency into account
I work at a large employer with 150 employees and no real cafeteria. So there a food truck makes sense.
They only do 1 hour at our gate. Quick money.
Plus fastfood is a 10 minute drive so a captive audience.
They just need to be reliable. Otherwise I pack a lunch.
So other use cases are weird to me. I can see festivals.
But the food trailer out front Lowes.
Who eats there? I rarely see customers waiting...