jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
The same way debasing gold coins is theft, even if the prices don't rise (because, say, you just conquered another country and got a new bunch of slaves to produce stuff). Claiming that inflation is a rise in prices confuses cause and effect.

As I said, this is rather well discussed by various economists. See for example https://mises.org/wire/inflation-beginners
Even if you were using pre-processed data, pattern matching helps to make the code easier to read. I guess I can think of clearer examples in other languages, like Rust, that supported tagged unions:

// Given this enum
enum NumOrStr {
Num(i32),
Str(string)
}

// That allows you to define values like this
let x = NumOrStr::Num(10);
let y = NumOrStr::Str("hello");

// And some random code that produces a value z that is of type NumOrStr
let z: NumOrStr = ...

match z {
Num(50) => println!("Got my favorite number: fifty!"),
Num(n) => println!('Got {}', n),
String("hello") => say_hello(),
String(s) => do_something_with_string(s)
_ => println!("Default case, x = {:?}", x),
}
I don't think it is offtopic or if it is then my mention of Rittenhouse in the first place was. I am very curious too. I have a pretty bad feeling that he will get off extremely lightly and that as a result the US will see renewed unrest. Given the original topic that kicked off this thread, the unrest will be entirely justified.
Absolutely. Pete Townshend's deaf in one ear and has severe tinnitus, and he doesn't blame Marshall stacks (or even the still louder Hiwatt amps he actually used), he blames headphones in the studio.

It's a very serious thing and it's dead simple to produce dangerous loudnesses, that close to the eardrum. What I ended up doing for tracking drums and loud things, is investing in some heavy isolation headphones, Sony drivers in the same kind of heavy tight enclosures used for ear protection at gun ranges. They're pricey, but they work.

Otherwise, you're still getting close to the sound pressure levels of whatever drums or amps you're playing, and then you're trying to turn up the backing tracks in your headphones to be enough louder than that, so you can hear what you're working on. And that's super dangerous.

Same thing with music to drown out noisy subway rides or what have you. You'll go deaf. Extra fast.
It’s all in the wording. I think the point is to avoid momentum and autopilot. But challenging yourself and learning new things doesn’t need to mean unwelcome stress or discomfort.
Absolutely, my point was that the social phenomenon of paying money for digital conspicuous consumption is already here with or without NFT's, though I'm solidly in the camp that NFT's don't add value in this interaction.

Taking what I had intended to say one step further, if you look at the denominator of "people who participate in digital conspicuous consumption," the NFT people that this article discusses is just a niche/fringe in a movement that already has lots of momentum.

Personally, I hope the digitization leads to far more people becoming creators and not just consumers, but I'm not holding my breath for that outcome.
> Average citizen preferences have no bearing[1] on the adoption of legislation.

Stated vs revealed preferences. Saying you care and voting like you care are 2 very different things.

> I cannot understate how much I disagree with the idea that politics was somehow more sensible "back then".

How did every country manage to come to an agreement on phasing out CFCs? How did the US set up the EPA? And can you imagine proposing something like a public library system today, if it didn't already exist?

Politicians were equally (or more) corrupt, morally suspect, and duplicitous in the past. I just think that they also managed to pass more legislation about things that really mattered.
Wow, you cherry-picked 10 seconds of video from 1000s of hours of content! Amazing work! That video was 4 minor versions ago also.
My bonafides for the comment I’m about to make: 5 years of professional Scala development at a serious Scala house. I have never done Haskell, but many of my co-workers have, and I had at least one interviewee do all his coding in it (he got hired, not because Haskell).

The problem really nice abstractions have is that they encode too much into too little code. They are very concise, and people who aren’t as knowledgeable (avoiding the word “smart” here as I think it’s wrong) will treat it as “magic”. Magic in code is a really bad idea when you need to debug it. The ML type system can create these magic moments that make someone who actually wants to understand how the hell that works have to go down a multi-hour rabbit hole just to figure it out. The best example of this that I’ve directly worked with is Finagle. If you look at the code for it, you’re very often left scratching your head trying to understand how it manages to get so much done with so little code. Having been there while it was developed, I will say it didn’t start off that “pretty”, it got there over 3 fairly major revisions to the underlying type abstractions. The result is beautiful, but opaque to most of the mere mortals that use it.

I would argue that Go has been successful largely because everything that’s happening is “out in the open”, where the average developer can see it. It’s a very different philosophy, one that I think the quote-creator aligns with better than your typical Haskell devotee.
> After the layoffs in 2015, even though the team shrunk, Gumroad itself continued to grow.

Hmmmm. Sounds weird that there were layoffs given that you could clearly afford to keep the employees? The company itself was raking in more each year.
There's nothing scary about these robots, any more than my Roomba is scary. They are tools, and like all tools, they can be used for nefarious purposes or for the benefit of mankind.
I'll be moving to another bank and I'm no longer in a position where I have to worry about stuff that happened back then. It's just kinda sad losing the bank that I've used for basic checking from living under an overpass all the way through home ownership. :(
Lucky you. I am not sure what I did differently, but I had those (including a custom script to run sa-learn on my "spam" folder), and ended up with close to dozens of spam messages per day anyway.
> They won't make a product for you and they'll make lots of money.

LOL probably true. I hope that doesn't become the norm however. I refuse to take the depreciation loss on a new car, and if cars can't reasonably be expected to last 20 years (with repair/parts availability) I'm not sure what I'll do. Keep an old Red Barchetta in a barn I guess.
Nope. Everything is green for me.
But yesterday was enough for even those in denial to see it.
No I don't either. But haven't taken a taxi in 10 years. Never used an Uber.
Part of the issue here too is that not only is US health insurance very expensive, but for all practical purposes it doesn’t kick in until you’ve had a fairly significant issue. So you are paying a lot of money for insurance you hope to never use, and in the event you need some kind of basic care you are still paying out - and have no meaningful negotiating power. I’m under the impression in most countries with single-payer / government run health schemes, you might also pay a great deal for your coverage, but that it’s all inclusive.
Caveat before reading my comment: this article is from 2007 and the scene 8 years later is pretty different but the spirit still holds, I think. The author also specifically placed "pet programming language" in the article's title which makes my reaction to it a bit unsound since, for example, Haskell is not a "pet programming language".

WhatsApp built a 19B product on-top of Erlang. I'm building our startup's product on a mix of Haskell and Erlang; so far it's going well.

There's pessimism in this article that neglects to acknowledge adaptability. I agree to a degree with the thought that if I chose to build our product on-top of Idris I would be spending more time building tooling and dealing with immature parts of the language than I would actually building the product.

This is not the case with Haskell and other innovative but mature languages / platforms. Once at a certain size we may need to train programmers or develop some tooling internally but I see that happening even with Java and C++.

If you can boot up the product with the language / platform effectively and quickly, it's good enough to tackle a 100M product and adaptability can take care of the long-tail.
>I don't install the Facebook app and don't give Messenger Lite access to my contacts

Literally doesn't matter what you do, it's what other people do with your data. I can tell from this guy I interned for 15 years ago that at one point he uploaded his entire address book to Facebook including my name, email and phone number because he still shows up in facebook recommendations to me today on Facebook and IG.

Never gave them access to my contacts either or even had him in my contacts but FB's shadow profile knows he knows who I am.
Justice? Checks and balances? Maybe non-corrupt people to go to

- to remove the corrupt

- to not have to deal with the corrupt ones
"My world is really about data structures."

Also good. I tend to take the perspective of features/impact to end users, so my feedback is about that. But great project to put your data driven back-end to a real use case as a way to learn and have fun with.

Another project that is bit 'on pause' that's perhaps more in your corner, is my attempt to set up a search engine for all charities, based on open data.

https://github.com/juliuszelf/global-charity-search-engine

Challenge is not even so much gathering the data, but figuring out a use case to make such a search engine valuable to a specific set of users, so it will get used, get feedback and can grow.
Android app: It works fine on my S10. It can glitch out sometimes, but that is rare. I admit I almost never use the offline functions. So maybe that part of the app is not well-made.

Web app: I don't use the web app.

Mac/Windows app: I use these and they work flawlessly for me. Maybe you can try this instead of the web player. Web apps are often trash, so I won't be surprised if Spotify's was too.
Textbook embezzling.
Reminds me of Google Meet: https://blog.plover.com/tech/ui.html

It probably looks great in a picture, but it's indeed a UX nightmare.
I read OP's comment the same way, but also think the counterpoint is valid.

People living in these "slow", offline first places are self selecting, and it's not for everyone.

My parents moved to a tropical island, have been there for decades now, they love it and will never go back. I also grew there but left at the first occasion and more than half of my schoolmates did the same.

IMO living there requires a distance from fast paced, online, strongly information based social discourse. If you don't have that you're in for a bad time.
Based on random googling I found this PDF:

https://www.gammabeyond.com/wp-content/uploads/2019/05/Why-C...

Page 19 talks about the history of the mini mill in steel production.
Yeah I don't believe tests will replace testers; tests are a safety net for regressions, a safety net to allow for refactoring without changing the in- and outputs, but they are NOT a replacement for testers who look at and work with things from a user's or a business' point of view.

I mean by all means, if a tester finds an issue, write a test to replicate it before fixing it so that it can't recur.

But also, tests are code and code rots. Changing that implementation entirely voids the test. And at some point your test codebase size far exceeds that of your implementation.
Obviously you overlay points, and not the whole map.

This way you can see how the slab references real life points, which you can show on a correctly scaled map.
> The point I'm making is that this isn't simply that "there isn't anything in our current geo-political makeup where enough countries meet to disprove the theorem"... the theorem holds up under any theoretical design.

No, it doesn't! Of course, as a true theorem, its conclusion holds whenever its hypotheses do—but there are hypotheses, not all of which are satisfied by any theoretical (or, perhaps more importantly, real-world) design.

One is that meeting at a corner is not counted as 'meeting', which you may fairly object is just a definition rather than a hypothesis; but another, which is a genuine hypothesis rather than just a matter of definition, is that the countries / regions must be connected [0]. (For a real-world example where this hypothesis is not satisfied—although the conclusion still is—on the level of states, see Michigan; and, on the level of countries, see the US and Alaska. I don't know if it is possible to make all countries connected by building imaginary land bridges across non-territorial waters, but I doubt it.)

EDIT: As Someone pointed out at the top of this thread (http://news.ycombinator.com/item?id=8801082 and then, in response to my confusion, http://news.ycombinator.com/item?id=8804876), this disconnectedness can actually create an issue; the fact that it technically isn't an issue for the particular case that he or she mentions is just because the regions involved aren't technically 'countries', rather than because no pathological arrangement of countries can break the 4-colour theorem.

EDIT: [0] Probably I should say 'open and connected', to avoid the pathologies a malicious topologist could cook up.
Yes. Using objc_msgSend and NSSelectorFromString, you can call functions, dynamically by name in Objective C.

Yes, it's dangerous. Clever, and not quite as easy as your favorite dynamic scripting language, but Obj-C supports it.

My favorite personal use case so far is an Objective-C state machine, where state names are strings, and state callback functions can be added to the code & called without declaration. It's not really saving much technically, but it eases just a tiny bit of mental & manual friction to be able to modify the code without having to update header files.
In terms of $/gram of Omega3, flax oil is much, much cheaper than fish oil.

http://www.amazon.com/Barleans-Organic-Oils-Lignan-16-Ounce/...

http://www.barleans.com/images/supplemental/ot-lignan12oz-su...

It also has a lot of 6&9. I'm assuming that still moves you towards a good balance. Can someone tell me I'm mistaken?
Engineering, to some extent, requires mastering the art of knowing when to temporarily abandon a project in the intest of shipping. A mature engineer has gone through this cycle multiple times to the point that the "abandon to ship" concept becomes part of his/her normal process. It's far too easy to keep at it and never ship anything.
> If the tooling for verifying C is really so good, why not verify the C parts of the JRE? Then they'd be proven once and for all, and lots of systems would benefit.

I'm going to quote the article again...

> You're more dependent on the decisions made by the language implementers than you think.

When you use Java, you don't have the opportunity to second-guess the choices that produced the JRE. And I think you're not quite getting what I'm saying: I'm not saying that "we should switch to systems which are written more in C", I'm saying that writing systems in C protects you from mistakes in the JRE (which you have no control over) in exchange for exposing you to your own mistakes (which you can control). You can then spend a large amount of time and money developing and verifying your system. The goals and constraints of your project will determine whether this is a good trade-off. I'm certain that Java is preferable for writing the vast majority of web apps, but the web is not everything.

> If the tooling for verifying C is really so good, why not verify the C parts of the JRE?

First, I'm going to guess that an enormous amount of static and dynamic analysis has been done on the JRE. Bugs in it are rather rare these days, given its size and complexity.

However, verification tools are generally not suited to this particular task. Verification tools are better at verifying typical application code, and the JRE needs to do a lot of very unusual operations in order to work. In cases where you'd use verification, you'd also typically use a "safe" subset of C. Some of these subsets don't even permit dynamic memory allocation, or if so, only permit it at program startup.

So, it may actually be more straightforward to deliver a working Mars rover in C than it would be to deliver a verified JRE. Neither task is easy.
What's a single example of a daemon with more than 10,000 lines of C code that will reliably "survive" memory exhaustion? By "survive" we obviously both mean that it retains its original PID. Of course, most Unix serverside code "survives" by simply aborting and allowing itself to be restarted. Since that's what I'm recommending, that strategy doesn't count.

To find one, you're going to have to catalog every malloc() in the entire program and record some kind of recovery regime --- maybe degraded performance, maybe dropped requests, maybe fallback to some kind of pool --- for every allocation.
You don't know. It's true that the line of code he cited was incorrect. It's just not a very interesting example of incorrect code.

Malloc failures don't always result in aborting. The common alternative, especially in programs that have careful malloc return value checking regimes, is to occasionally cough up remote code execution.

Userland systems programmers should assume the conservative default of ending the program immediately when malloc fails.

A similar logic guided C++ into throwing bad_alloc instead of returning NULL on allocation failures. And a survey of modern C++ code will show you that most C++ programs simply allow themselves to terminate when bad_alloc happens.
The full transcript of Crichton's lecture at Caltech: http://stephenschneider.stanford.edu/Publications/PDF_Papers...
I think it's much more likely we'll continue to do what we're doing now: printing money and reducing the value of existing debt via inflation.
What parts of Singapore? I've been on the streets here for the last two years, and honestly don't recall much smoke, as compared to California, or Vancouver - both of which also have strict anti-smoking laws, and which I'm frequently assaulted by smoke - though a lot of the smoke in those cities is cannabis, which obviously isn't a problem in Singapore.

Perhaps it's because the areas I go to (Labrador, Harbor Center, Orchard Road, Woodlands, Holland Village, Botanic Gardens, Newton) are more smoke free?

With that said - I just did a survey of everyone in the room, and they indicated it's no better than anyplace in Canada - so perhaps I've just been missing something.
And apparently coincides with what little tropic forests are left?
I wonder if it’s intentional that Facebook products were omitted from Apple’s list of apps to download for new iPhone users:

https://m.imgur.com/yT14ZVS
thanks for the CSS.

I like the padding, because this adds a great space in the div

http://cl.ly/Z83l

about the border, I'm not sure.

I had thought about cookies ... , but first I try to focus in a preview more similar to the final presentation and how to use more than one theme.

thanks again :)
Earlier discussion, including a number of comments from the author, here:

https://news.ycombinator.com/item?id=4407188
I recently (2 months ago) started using Cloudfront (on Mugasha.com) for all our static assets. Images, CSS and JS so far, going to move to audio and video assets to Cloudfront spill over soon.

Setup is pretty straight forward, it took a few days to get it right. The main problem with Cloudfront and S3 is that it does not GZIP the files for you on fly based on headers (if browser accepts gzip).

So here is the process I have setup for a rails app.

0. Store all the static assets paths in a config file. LIke this http://grab.by/51Zh. Then I modify the CSS and JS helpers with something like <%= include_stylesheets :common, :media => 'all' %>
1. Make changes to code (js/css/images)
2. Create a folder on s3 with a unique name based on the commit and time stamp. Store that folder name in some config file.
3. Run a script, that uploads all the images to cloud front. Then does a replace in all the CSS and JS file for image urls that are cloudfront based (asset1-5.mugasha.com for background images etc) Then combine, minify and compress/gzip css and js files. Upload files.
4. Commit and deploy.

Each time I run the script and deploy, the asset urls are automatically generated.

I am not sure if this is useful info, but I wanted to share anyway.

I am using modified version of Jammit http://documentcloud.github.com/jammit/
"Virtual addresses are the size of a CPU register. On 32 bit systems each process has 4 gigabytes of virtual address space all to itself, which is often more memory than the system actually has."

I guess this is not the most up-to-date document?
> Isn’t this how stock markets work? Actual company performance is just a relatively minor signal for the chicken.

In my experience, actual company performance is a very huge signal. You just need to zoom out and look at longer timeframes. The stocks with the highest prices and gains over the long term are those with the highest profit and growth potential.
If anything, the fact that we’ve all been watching this supposedly forbidden video across social media sites shows that the technique doesn’t actually work.
Yeah, the M7803 is great. Still have the one from my G4. A couple of years ago, I found a guy on FB market place that was clearing out an office with a bunch of those. Bought two, a black/clear and white. With those as backups, I took my original one apart to give it a good cleaning.
Agreed, Swift has an obsession with functional programming that is just so off-putting to me and I suspect many others.
>>> After boot I can pull out the stick, freeing up the USB port for something else

Does this mean the entire OS is loaded into memory? Is this a NetBSD thing?
Marketing for unhealthy foods is a 20th century thing. And marketing something as healthy when it's actually not (fat free craze of yesteryear). To me it seems this is one of the major problems. Lack of education on healthy eating, damaging advertising, and a lack of regulation around food labeling.
Slightly related, we're working with a similar philosophy. As a machine learning consultancy that has done many learning projects for enterprise, we're building our machine learning operations, "MLOps", platform (https://iko.ai) to simplify our work. However, what we're doing is working from the architecture level to have as little and preferrably no sensitive information on our service. We're architecting it so that you give us specific access to deploy on your cluster, and everything happens there: the notebook servers are there, your data is where you choose to put it, your training jobs are there, your experiments are tracked there. Your models are deployed there.

I have a saying that the platform should be able to run on a Raspberry PI.

One of my personal pet peeves working with the team is to be able to disappear without impacting them, and it has become the same with our platform: it must be able to disappear users having to scramble to exfiltrate or export their work or data from our infrastructure, because it simply is not there.
Apple churns languages every few years? They kept Objective-C around for 13 years before introducing Swift, and that was a language that was widely disliked by people from outside the Apple ecosystem. You can still use it for the vast majority of OS features today[0], nearly 20 years after it was first used on Apple platforms. Heck, Obj-C is used for Mac/iOS development because that was the preferred language for Mac OS X's immediate ancestor, NextSTEP, which means that it's been a part of the same development ecosystem for about 30 years. If this is churn, I think I'm okay with it.

[0] As far as I know, the only system feature that requires Swift is iOS 14/macOS 11's new widgets, which must be written in SwiftUI.