skysight-inc/HackerNews huggingface dataset:
A regret: never being able to afford university and always feeling like it was too late when I finally could.

It turns out I really enjoy type theory, category theory, and formal mathematics. I also care about liability, reliability, and safety. And all I can do is study in my own time, which I do freely, in order to catch up. And I will never get a research position or work at a startup where I can put these skills and ideas to the test.

Oh well. I will still work on the libffi integration in the community Lean fork and will try to get Lean working on AWS Lambda and GCP, etc.

If you're younger and starting out -- don't neglect maths! It is far more useful than the programming language du jour. The former is how you weather the constant flux of the latter. And how you solve hard problems.
I would agree that Math is useful in several programming situations. I won't say that I shouldn't have maybe tried a little harder to understand it. Here's the problem though, nothing's free. Concentrating more on Math, means you have to give something else up. Maybe Math would have helped you in a certain situation, but what other skill have you gained that are useful in others? It's easy to say, "Wouldn't it be nice, if I did this?" without having to specify the consequences of that action. (OK that sounds really negative, but I'm sure you know what I mean.)
This makes sense but I'm guessing there are diminishing returns that may actually turn negative at some point.

I.e. How much more likely is someone who watches 21 hours vs 20 hours to be retained? Then how much more likely is someone who watches 41 hours vs 40 hours to be retained? I'm guessing that on average there is a much smaller difference between 41 and 40 than between 21 and 20.

I'm also guessing it may turn negative as some people have shown they will subscribe for a month, binge on their favorite/new shows, and then cancel. Perhaps renewing in a few months time to do it again.

Would also be curious about other metrics such as search time : watch time. I'd imaging people spending more time searching and less time watching get frustrated and are more likely to cancel. With autoplay it eliminates searching for some.

I'm also curious why there isn't a setting to enable/disable autoplay.
Most users aren't updating at all. My highly educated STEM employed wife just hits the "not yet" button on all updates. But when disclosures get enough attention that it leaks into the broader (not-security focused) information ecosystem, people are more likely to upgrade- remember how suddenly everyone heard about Heartbleed (e.g. my mother-in-law asked me about it)? That's because for all that we steely-eyed engineers said "cute names? Logos? This is fake, it's all about the ideas, not the fluff" that fluff caused the message to be amplified and more white hats learned that they needed to upgrade. The bad guys knew immediately, because they are paying attention. Most of the good guys aren't, because they are busy earning a living that, fortunately for them, doesn't revolve around computer security.
I guarantee you his/er knowledge was probably a 3 or lower. If this were reddit I would ironically reply they clearly were just jealous of you or didn't believe you had such a well-developed grasp of C++ fresh out of college.
ECB: Behind the scenes of the beauty contest: window dressing and the G-S (cont) [pdf]
When I was managing a deep learning team last year, my boss’s boss asked me if I had looked a Julia. I had not, but promptly spent a weekend playing with it. The deep learning library Flux is very good, GPU setup is really easy, and I wrote up snippets for text processing, web scraping, simple NLP, etc. I was doing a personal evaluation to see if it could be a language that I could do everything in. The answer was ‘yes’ but I ended up sticking with a mashup of Common Lisp and Python for my personal projects.

Julia is a fun language to use because it has a great repl and a pleasant enough syntax.
> Why can't download the photos directly to a phone?

You can on some cameras (e.g. Canon 80D), but it’s somewhat cumbersome and eats batteries at a fantastic rate because the camera hosts its own WiFi access point.
My guess is that Canon is afraid of cannibalizing sales of their cinema cameras, like the C300.

Panasonic and Sony don't seem as worried about cannibalizing theirs, which might be a better strategy in the long run. Fuji and Nikon don't sell cinema cameras, so they have no incentive not to move fast on adding video features to their (previously) still cameras.
Indentation sensitive parsing the easy way
I agree.. it’s not something that comes naturally. Encouraging this kind of culture/discipline is hard, but worthwhile. I think it’s better than the alternative of getting hounded by PMs all day. Like it or not, estimation, deadlines and status updates are part of any commercial engineering endeavor. I’ve never worked at a place where “It’ll be done when it's done” is the way.
"every one of the major features listed in this post replace an existing language feature"

That is the part that annoys the hell out of me in regards to C++. Nothing ever gets replaced, things just get added on top of everything. And to add to that there is generally very little indication which is the "new, safe and cool way" and which is "old, shoot yourself in the foot" way of doing things. Like std::string is cool and generally you want to use it everywhere... except you can use []char everywhere and be completely unaware that you are doing anything wrong (well, until you segfault on memory access). Or unique_ptr and shared_ptr and auto_ptr. Cool things, but you can use a regular pointer in their place and again, never realize something is wrong (again, until you segfault). And every C++ book I ever saw happily discusses raw pointers and memory allocation and []char strings without ever giving you any warning that under most normal circumstances you should not use any of this.
How to start a software YouTube channel
From what I recall from various forums and reddit threads it was not just users who generated sexually explicit content, but any streamer judged to be a “thot”.
I used to work for Canon in a different division. It was an interesting company to work for, fantastic human-perks
i.e. 2 weeks paid time off (not counted against vacation) if you got married,
1 week of paid time off if you moved. (not counted against vacation)
You got your birthday off (paid and not counted against vacation).

Upper (middle?) management were all dinosaurs, and stuck in their ways. The entire 'digital revolution' caught them unaware and unprepared. And most importantly IMHO, they didn't eat their own dogfood. The only saving grace for the printer/copier division was HP's controller boards and drivers.

This was a situation where you knew you were on a sinking ship. Some R&D and advancements were INCREDIBLE, some of the behind the scenes tech was very compelling but I don't think management could get out of the way.
...maths is not a formal language by any stretch of the imagination. I think about the best definition one can give is maths is what mathematicians do, and maths notation is what one mathematician writes down to communicate mathematics to another mathematician.

It's circular in about a dozen ways but that is as it is IMO.
Also no perfect vacuum exists which renders this rather irrelevant for discussing what happens in real situations. I also did some reading to figure out the correct terminology - it is certainly correct to say that a perfect vacuum has no thermodynamic temperature as it is defined by the state of motion of the particles making up the system you want to assign a temperature to, however I am still not convinced that it is wrong to associate a temperature with a vacuum based on the electromagnetic radiation filling it.
Excellent points. I want to follow up with some back-of-the-envelope math on this later, if I have time. My intuition was that it takes a whole heck of a lot of fuel to get someone to even LEO velocity. Would love to see how that corresponds with air travel.
I think photolithography blows literally anyone's mind.
The ones that matter already have Metal support in place.
Back when I was doing a lot of 3D and other work that required Photoshop, I used a VM in Linux to make that work. This was back in 2008-2009 though, so I'm not sure if others do that anymore or just use a different PC, other software, etc.
> Except the security community and Google inclusive have no freaking clue who or what has discovered those exploits. And now they're available to everyone.

They were already available to everyone. You just didn't know about it, and now you do and can take protective measures.
I'm not missing that point. "Which is better" is not measured by who has "information". If only the bad guys have the information, but they still fail to exploit, that'd be an awesome world. Somehow infosec folks seem to keep treating this as an information game rather than a security game.

The way I'm suggesting you measure "better" by measuring actual hacks, and how the number of actual hacks is changing based on whether you insert a delay or not.

So we go back to my question above, which you didn't address. I'm saying the fact that patches come out on a regular basis means that people would still have to update regularly, even if each individual patch comes with a delay before a PoC etc. is disclosed. So I repeat the question: would customers really update regularly but actively filtering out patches whose disclosure deadlines haven't passed? If not, why wouldn't the delay that still achieve the outcome everyone is asking for here?
The early Betamax recorders didn't have a timer on them. Plus the tapes were super short. So if you had a show at 3pm you wanted to tape, you had to be there at 3pm to push the record button, then be stuck with only 90 minutes of recorded content.
> I'm not saying the name is wrong because of the comment, I'm saying it's wrong because of the usage of the acronym.

I get that. But you also said the comment would be unnecessary with a name change. The comment does communicate more information than your proposed name, IMO, hence is not replaceable by the name. (IMO).

> You wouldn't get a different rounding if you were to modify MAX_TIMESTAMP_PRECISION, which is what you would expect based on that comment.

Good point. The comment isn't wrong with the definition of MAX_TIMESTAMP_PRECISION as it is in the code. If you override it though, the code doesn't do what the comment says.

It's an interesting case: if you trust the comment indicates the desired behavior, then you can see the code may have room to be improved. If you distrust that the comment is correct or has value, then you might just remove the comment, and the code doesn't get better.
Compiz cube was what convinced me to try Linux in the first place - I had always thought of it as a boring server OS, but then I saw the desktop cube and wobbly windows and thought "that looks cool enough to try it out." Hopefully this could have a similar result for some people who have VR headsets.
The advantage of microkernels is that they can be extended with “untrusted” code like hardware drivers or file systems. This runs in user space and thus any bugs in such code will not crash the kernel process.

So I agree with you that Linus is presenting a straw man and your comment shouldn’t have been downvoted.
I think the whole idea of simplicity vs complexity, and the linked article "Worse is Better" is fundamentally ill-conceived. Simple vs. Complex is contextually relative. Literally every observer is subject to their own opinion of a design. Success in the wild = success. I think success in the wild, especially in our age of information overload, depends on being "convenient to understand and operate".

A 'simple' solution may not be easy to grok. Few people think at the level of axioms.

A survivable solution must be passed along to many people across generations.

For some, monorepos are simple because that is what they know, for others multirepos are the norm. The survival of the firms that adopt these strategies will somewhat dictate what repo strategy propagates in the world, not the best design.
I am probably a minority but I hate live viewfinders as looking at a tiny screen, despite the benefits live exposure composition offers, gives me eyestrain and headaches. I much prefer an optical viewfinder so for this reason I really hope the mirrorless hype isn't going to displace DLSRs entirely and Canon keeps making them.

Bit of a moot point for me at present as all I have is an old Lumix LX1 with manual settings that still takes good photos at 14 years old (just super limited due to sensor size and a 400 max ISO) and had to sell the DSLR for financial reasons. Still have a dream to get back into photography if things ever look up enough I can justify spending on a hobby. I really enjoyed it. I would love to do some astrophotography especially. Even an original 6D (superb low light clarity) and the right lens would probably suit me for life with no compromises to my interests as long as I could keep it serviced and alive. Tried shooting the Milky Way recently with the LX1 but the low light ability won't allow it.

Bright side is maybe even if mirrorless is the future, it would make DLSRs more affordable used as people sell off the "deprecated" tech.
> What's missing from these conversations is realistic approaches to fixing it.

Do you really want to mandate that?

Valuing someone's personal information at $100,000 per person and then fining the snot out of companies that lose it seems like a much more "market driven" solution.

It also means that companies will work really hard to minimize any personal information at all--which is really what you want in the first place.
There's a lot of potential value in influencing public opinion.
Hmm, according to panopticlick, my Chrome provides about 70 bits of identifying information. There are about 2^33 people. I don't feel incognito.
Another place where I wish I knew more math is Programming Language Theory. Proofs, abstract algebra, Denotational semantics etc. This would've let me work through books like Software Foundations, TAPL etc.
Civilizations started around 12ka ago. Neanderthals went extinct around 37ka ago.
It's a major problem still: teachers neglect giving examples of practical application of a given concept (might be difficult at times, I admit), and miss the opportunity to make knowledge stick and increase the intuitive understanding of the subject.

I still remember my dialogue with my high school maths teacher when first learning calculus, it was more or less along the lines: "But why do we need these differentials?" "Because it will help you to understand integration." "But why do we need integration?" "Because it will help you in your further education." (No, she didn't even mention velocity/acceleration or area below the curve as it's usually done, I had to figure these out myself.)
Good on them, seems like a good business model
The Soul of a Start-Up
You could certainly see it that way, but I found that it is a good example to illustrate the intention of having a very simple syntax and processing logic (up to the point where arithmetic expressions are not what you expect them to be).
What mathematicians DO is computation.

What a mathematicians WRITE is a formal language used to express computation.

Manipulating mathematical expressions has a name. Symbolic Computation.
https://en.wikipedia.org/wiki/Computer_algebra
"The FACOM128B greatly contributed to technological advancements during the period of Japan’s high economic growth from the early 1960s to the early 1970s. The computer was used in the design of camera lenses and the YS-11 plane, Japan’s first passenger aircraft developed after the end of World War II."
Really handy post. Looking to do a similar thing
Your vision is extremely compelling and well articulated.

I'm not sure I buy the "coalescing multiple things into one makes things simpler" argument - the simplicity comes at the expense of expressiveness, flexibility and optionality. A large, highly-opinionated monolith, right the way across the stack, is bound to have made some design trade-offs and decisions that are either plain wrong (we all make mistakes) or don't fit with however I want to actually use it.

To do this at the AST graph/language level strikes me as both genius and absurd - not only is language design very hard, but you clearly have a massive uphill struggle to provide sufficient library and framework-level code on top of that to be able to start to compete with more mature options. Not to mention things like code review tooling (it's neither text-based, nor even in any form of conventional revision control system, so likely start from scratch). Security controls, auditability, vulnerability management for any library ecosystem that springs up around this, etc. etc.

By rejecting text you are having to reinvent and support a compiler, an IDE, github/gitlab (or equivalent, with their massive functionality set including protected branches and security controls and the like), package management maybe, debugger tooling (on the web), release/rollback systems/UIs, perhaps even monitoring and alerting (because you're promising the users they don't need to run infrastructure/services like Prometheus and the like and your "roll out" process looks so different).

Does Dark really have sufficient expertise around all of that to want to make this stuff totally monolithic? Is it even possible for a startup company to really compete in that sort of global (massively open source) scene?

Convincing people to bet their company on your company, both as an ongoing enterprise and as a place that can get all the inherent trade-offs here well-matched to their individual use-cases is going to be an almost impossible sell. Regardless of how much you assert that you believe in your mission and don't want to ever pivot. You can't blame people for being sceptical, especially when the opening paragraphs essentially say "this is a silver bullet".

I wish you luck.
I need to go home and eat a bunch of weed edibles so I can read this comment.
Did you just invent the unikernel?
I'd suggest reading the wiki articles about it for an introduction, and Ch 5 of https://www.amazon.com/Computer-Architecture-Quantitative-Jo... for a detailed understanding.

Right now you're asserting things about all this, while not being familiar with relatively basic aspects of how it works.
> there is still a large market for larger sensor cameras

It's large, but shrinking according to:

https://petapixel.com/2019/07/08/canon-increased-market-shar...
Hence why no single games console makes use of OpenGL.
Apparently people lie about what music they like
Related to this, check out Dakshana (https://dakshana.org/ ). They're a very well run charity with great metrics, and their Annual Reports are interesting reading.
Do you have ongoing guaranteed yeld for coal plants? That's insane. Is it some old contract that is about to expire?

Anyway, I wonder how the grid will cope after the lion-share of the generation is done by synchronized inverters, instead of high-inertia rotational generators. I am concerned we move too fast and make our grids instable worldwide, with generators amplifying deviations instead of absorbing them.
(I wrote the post.)

If it's helpful, I dropped out of both schools — the vast majority of my knowledge is self taught!
The Nanosheet Transistor Is the Next (and Maybe Last) Step in Moore’s Law
I'm sort of against it, but Notch got the Minecraft generation hooked on it!
If you're "not a Republican or a Trump supporter", you maybe should be glad that independent advisory boards exist. Someone has to say "your plans conflict with reality" (when that's accurate), and it seems unlikely to be the people Trump surrounds himself with...
Maybe you can pawn it off on the Algolia people under the guise of a Smarter 'Past' Button Challenge!
> every one of the major features listed in this post replace an existing language feature with something that is easier/safer/less verbose

I'd argue that the each new feature adds on top of an existing one. 30+ years of existing knowledge won't vanish, and will cause decades of unintended Frankenstein codebases (followed by decades of even more Frankenstein ones).
From 0 to 70% Market Share: How Google Chrome Ate the Internet
Standalone Lexers with Lex
For a lot of kids its the only way out of the hood. Especially these kids in super 30. If they don't make it its back to poverty. If they get in they have the ability change their entire families socioeconomic status including parents and siblings. Its like pro athletes or rappers trying to get out of the hood. Its hard to do.

To a lot of kids it is a life or death situation.
I don’t think Pixar’s Maya-like software ‘man v’ runs on macOS, at least it didn’t a couple of years ago (my ex was a TD at Pixar and used to complain about the old version of Linux they were on). I’m pretty sure the demos they showed were of their file format viewer which is a separate thing.
That's probably more related to you paying 5x more, and not the brand...
I'd say just make sure you have some practice using a version control system and know the basics of making and merging branches. You don't have to be experienced with handling merge conflicts, when you're on a team a more experienced person can always help you with tougher cases like that.

I'm assuming you have some projects at home since you're self taught. Whenever you find yourself manually checking something works on these projects, consider writing a test. If your compiler/build system doesn't have a test framework built in, you could just write a little command line program that prints pass/fail at the end. Test frameworks are easy to learn later. The skill to develop here is knowing how to write testable code--i.e. if you can't test something without running half your code base, figure out how to decouple the thing you want to test from everything else.

Companies all have their own quirky processes for things like code review, and very few are actually following best practices, so for this you'll learn how to do things when you get there.

More important than anything I've written above though, is have some experience reading other people's code. Writing code does not necessarily make you good at reading it. I'm self taught, and I used to have a pattern of downloading an open source library I wanted to use, trying to do something in it that went past the basic examples, and then giving up because the documentation was awful. When you work for a company, you're usually surrounded by code you didn't write that has little to no documentation, so you're gonna have to learn how to read code to answer your questions in order to be effective. If you don't know how to practice this, consider downloading a little open source game you like, and try making simple changes to it. Navigating a big code base you didn't write is pretty overwhelming at first, but it's an important skill to develop.
I should have been more specific. I was referring to the question about what happens when roommates buy a couch together in order to illustrate it's not quite the same.
VHS and Betamax was maybe influenced by the adult industry (although sports seems to have mattered as well)

Parroting the same about HD/Blu-ray is kind of hilarious though. Porn was deep into the streaming game long before blu-ray hit the scene.
The field?
Sure, but there are several arguments for doing code reviews/QA/etc that are already convincing. Its interesting.. but I guess I don't see how we can use this new way of looking at code transformations to our benefit.
https://www.collabora.com/assets/images/blog/xrdesktop/xrdes...

Oh god... where's your anisotropic filtering? That looks like a screenshot from Doom.
Thread from 2017: https://news.ycombinator.com/item?id=14002380

2014: https://news.ycombinator.com/item?id=8443028

2013: https://news.ycombinator.com/item?id=5030309
So you are concerned that they are improving their competitors products but not their own? Doesn't it make more sense just to not do pro-bono research for their competitors?