jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
I am surprised news outlets are still trying to give life to this manufactured crisis. Who cares what Neil Young thinks about any of this? Why are these celebrities put on a pedestal by news media and individuals? At best, Neil Young is a has-been whose music will soon be forgotten by newer generations that have long since moved on.

More importantly, Neil Young has shown himself to be for censorship and against the free exchange of ideas. His stance is fundamentally at odds with free societies that harbor enlightenment values. The problem is not Rogan or Ek, but Young and the new authoritarian pro-censorship/deplatforming political tribes, who abuse their voice and power to silence those who don’t share their ideology. That’s not the stance of reasonable people - that’s the stance of zealots, no different than religious zealots of a different era.
Yep, fake it til you make it. Look at how much money Amazon/Lyft/Instacart have lost, profitability is only X years away! (to be fair Amazon did make it)
Setting KDEWM to something other than KWin no longer works in Fedora as of 35 (and other "leading edge" Plasma distros like OpenSUSE are quickly approaching this turning point as well). There are several spots in the Plasma code base that KWin is hard coded. Those distros that still allow functional KDEWM only do so because their version of Plasma is either not yet new enough to be affected, or they have deliberately held back parts of Plasma (which means at some point they'll have it give in as well).
It's logically fine to reject axioms. You could argue, for example, that torture is morally good because you disagree with the axiom that suffering is bad. That's logically consistent, and logic alone is built on axioms and therefore cannot discern which axioms are "better."
As a manager it's my duty to create a safe space and frame the challenge in a manner that doesn't create friction in the team. When an engineer says it takes 4 weeks I well and truly trust them, all that I seek is why. Because whey they then get down to one or two level deeper details they typically uncover more unknowns and for all you know it may in fact end up as 6 weeks.

Also, none of this happens on the spot; as in "tell me right know why it takes 4 weeks, let's do a 30 mins white board session". Having been an engineer I totally understand interruptions and, as a manager, interrupting my team is like shooting myself in the foot. When I say "conversation" it happens asynchronously over several days. I encourage them to spend a day or half a day to work out task break downs and dependencies because it takes a different frame of mind to "plan" a task as opposed to "working" on them.

> Are you truly going to lose customers, or are you just trying to pressure people in "being accurate",

It's a combination of both though I wouldn't phrase the latter as "pressure" or "being accurate". It's a way to discover information that will increase my team's confidence in delivering the project. As we all know most of the project failures are not because people slack but because they uncover a dependency too late down the line or they don't validate an assumption or a new constraint is discovered. Most of which could be accounted for with a simple planning process.

I do recognise though that most engineers don't like planning or task breakdown and so I spend quite a bit of time to take much of the heavy lifting so that they don't spend more than 10% of their time on it. As a manager I am held accountable for my team's delivery and I absolutely want engineers to be spending most of their time on writing/delivering software. One example is I don't ask for plans/task-breakdowns for anything less than a week. In fact there's not even a debate; on the contrary if an engineer says 3 days I ask them to round it up to 5 days (a week). Only for tasks that are longer than a week I may get into the details and for more than 2 weeks it's almost mandatory.

> developers say things to get managers out of their hair

This seems like a well and truly dysfunctional team. Engineers and managers are partners and only when they work together can they deliver something meaningful. I would address this mis-trust or friction first because if there's no transparency within a team then all bets are off. We'll end up with a series of failed projects, burnt out engineers, operational nightmare and what not. What I've noticed is these social frictions end up manifesting as "estimation problems" and people try to address the symptom by trying out different project management processes each of which fail spectacularly.
Here's one for Python. http://pythontutor.com/ It shows the variables, and allows you to step forward and backward. Great for explaining programming to new people who haven't grokked computing yet.
So in order to start breaking Zendo, you need to break AES-256 and SHA-256?
It's not exactly a neutral source. I would neither trust drug proponents for the advice or take the risk, for that matter.
And for more contrast, author of critique article can only brag "past few months I’ve been using Go to implement a proof of concept program in my spare time". I really hate articles from noobs who thinks they have a right to criticize something without being proficient in it. And not only about Go. At least HN comments are interesting.
As far as I know it's already a scientific fact but this time it is going to become "official". You can deny what has been figured out in a laboratory on a humble group of people (let alone mice) but you have little choice but to shut up once thousands of people all over the country get cured this way without going nuts or "becoming prostitutes" ©.
You can use emacs and tramp to edit files remotely within a local buffer. If you lose connection it doesn't matter, you still have the file, and when you save it auto connects. I often use this with Python and can execute the scripts within emacs with the results being sent back to another buffer.

You can also use eshell or even just shell (if you're not into lisp) within emacs once you are on the remote machine to execute bash commands, with scrolling.

I think that's what is being referred to, but I'm no expert.
Water molecules are smaller than air though, so a surface can be airtight and not be watertight.
> Then again, not knowing anything about Jennicam while she was online, I reckon any popular Twitch streamer has at least 100x the audience that Jennifer had.

IIRC, she got a lot of media coverage at the time due to the novelty of what she was doing, e.g.:

1997: Jenni, Jenni, Jenni: A Life Laid Bare on the Computer Screen: https://www.latimes.com/archives/la-xpm-1997-oct-01-ls-37894...

1997: Voyeur Eyes Only: Jennifer Ringley's real-time web of life: https://www.washingtoncitypaper.com/news/article/13013765/vo...

1999: 'Ed' of the Internet: JenniCAM going strong after three years: http://edition.cnn.com/SHOWBIZ/Movies/9903/26/jennicam/

Her audience probably was smaller than many streamers, but my guess is she was more well known across a broader slice of the public than any streamer.
If a broadcasting area can be 10 square kilometers with 100,000 people in them, and you need 40 base stations for $5000 to cover that, I feel like the infrastructure investment is insignificant compared to the engineering effort. Apparently the market exists.

In the US you could even transmit FM radio at the legal power levels from the base stations too, reaching like one apartment building from each base station.

A bigger legal problem is the copyright question. You could start with music from Jamendo and the Internet Archive but sooner or later your broadcaster DJs are going to want to broadcast Lindsey Stirling or One Direction, and then you'll have to prove in court that it's legal!
In IT field, latest technology is still considered as greatest.
It's the difference between thinking about moving your arm and moving your arm.
Yeah, those losers. They really should have just said "Hey, we're releasing a brand new feature called FaceTime and we need you to change your apps name. Oh yeah, and just don't tell anyone. Thanks!"
Wow - this is good. He can sing.
You can also open a SQLite database with the filename ":memory:".
Between our three founders we have three wives and four kids, so I can relate. How do you guys plan on raising your Series A funding while also keeping your cubicles warm?
File this under -> Gladwellian Pop Psychology.

I recall learning about the exact same thing 10 years ago in Psych 280. This is a Psychological phenomenon that is actually studied academically. So, "Pop Psychology" probably isn't accurate. Okay if you think it's BS, though :)
So in other words, everyone in the world will be using the iPhone with their favorite carrier, and thus competes equally with Android, except for people in the States who will be stuck with AT&T for a few more years.
I have a feeling that STEM isn't going to change anything, people want to believe whatever they want to believe and they are not going to let the facts stand in between them.

Take Intelligent Design as an example. There is a shit ton of evidence that proves that it is all a bunch of bullshit, but it doesn't matter because a lot of people want to believe it, so that is what they do.

So sure it would be nice to know the answer, but it isn't going to change anything.
Bio's not a joke, I actually design nuclear reactors. In fact, my experience in that field is why I believe what I said above.

The SL-1 nuclear reactor accident (possibly murder-suicide) happened because a human was actively actuating a control rod by hand and pulled it out too fast. Passive systems that limit rod withdrawal rate are better.

The Three Mile Island accident happened because a sensor mislead the human operators, who then did the wrong thing and ended up dropping the coolant level below the core, which subsequently partially melted. Passive safety systems like a pool of low-pressure coolant preclude this entire class of accidents.

Chernobyl happened because humans could and did manually disable all the automatic safety systems that told them the reactor was in an unstable configuration. Passively safe reactors can't physically get into unstable configurations.

Fukushima had active cooling systems powered by diesel generators. After the earthquake, they started up and worked fine. But when the tsunami came, it flooded the basement. The operators for god knows what reason put the fuel supply and electric switches in the basement, which flooded. The active safety systems failed, the coolant boiled, and the cores melted. As with TMI, passively safe reactors with low-pressure coolant and/or natural-circulation driven decay heat removal (i.e. no diesel backup power needed) would preclude this condition.

The nuclear industry is very into passive safety features, from experience. The first true passive safety demos happened in Idaho in April 1986 (weeks before Chernobyl) at a reactor called the EBR-II.

In summary, making a system safer with active systems is one approach. It's often both more elegant, more reliable, and cheaper to improve a system passively via design ingenuity. Thus, passive safety has a place here at Hacker News.
Here's an example of building a BASIC interpreter in Racket: https://beautifulracket.com/basic/intro.html
you don't need the stones, just the money! Seriously though, check out 24 Hours of Lemons. We race in it. Its the best!
And that's how people miss the opportunity to make a lot of money because they don't understand the needs of corporations.
Something I haven't seen mentioned much is that this is going to be one of the only cars on the market that you can fix the exterior on with plate-steel and a welder. In terms of apocalyptic vehicles, this is amazing. Also, in terms of me fucking hating curvy bullshit that nobody can work on without special tools... I really like it.
Similarly, by having the AND start in each subclause instead of being at the end of the previous clause, it's easier to "--" comment out specific clauses during development. Again, harder to read, but easier to work with.
Nothing about Google killing products is quiet anymore. People have noticed, and I wonder if Google is really aware of the extent of the brand damage that headlines like this cause.

Printing is the most corporate thing I can imagine, and even though it is not directly related, as a G Suite customer, this would make me extremely nervous.
Count up the collective hours spent figuring out why your printer no longer works and finding a new solution.

The vast majority of people using it won't see this news.

If Google doesn't make the Chromebook transition seamless and invisible, it'll be even worse.
They might not be wrong. Engineers who could be maintaining mildly profitable products could be invented new products that have some percentage chance of being much more profitable. If someone did the math and said the expected value of "engineer working on new projects" was bigger than the expected value of of the the profits of an existing project divided by the number of engineers needed to maintain it, then it'd be logical to abandon a bunch of seemingly profitable products. Bad for PR and for getting folks to trust you on new projects, and you'd need to bake that cost into the calculation, but still potentially the right call.
Oh... we did so much more than just let the Nazis use our railroads. War-profiteering is the word not used by Swedish media and politicians because it's such a dirty word.
I'm missing the irony...
>After five or six lines he stopped, scratched his head, looked at the proof, and crossed out the last line he'd written. Then he looked at it some more. After a couple of minutes he looked up, apologised, and said he'd got stuck and that we'd go back over it in the next lecture.

He probably just proved the Riemann Hypothesis in his head and got distracted.
You understood correctly -- has Netflix since added a lower bitrate for 3G? The last time I tried to stream over AT&T it would buffer about five seconds for every one second of video.
I think it's important to remember what IDE actually stands for: integrated development environment.

That implies that the standard development environment used to not be integrated. And that's exactly what Unix is: a development environment where the tools are not integrated into one place. That sounds like a bad thing on the face of it, but I do not think it is. I think it allows for more flexibility.
What the hell is going on here? What is Cultured Code? Why is this guy so opinionated? Who is he? Why should I care? What is this "wallpaper" he is referring to? Are OmniFocus and Cultured Code two competing software suites? What do they do? This site gives absolutely no indication of any context.

Ah, okay. Upon forcing myself to read the rest of the article, I infer that Cultured Code is a blog maintained by the guys who make this software called "Things," which I had no idea existed until just now. And I also infer that the guy who wrote the linked article (I have no idea who, of course, because the site has no author listing for its posts and no "About" link to be found) is kind of an obnoxious blowhard. As a fellow obnoxious blowhard, I applaud his ranting chops, but I guess I just wasn't the target demographic for this post.
Arctic Startup is a good example of a niche blog that has been able to generate reasonable revenue. Recommended reading.
It's even more nuanced than that: the Squeak project took the time to actually do a full hunt for all of the old contributors, figured out who they were, rewrote their code when necessary, and got signed legal agreements authorizing the relicensing of their code under the MIT license. The Pharo project took a more practical but somewhat more cavalier approach without the lawyers and signatories. So there is actually the chance, though I want to emphasize very strongly a ridiculously tiny chance, that something in Pharo is incorrectly licensed at this point, whereas Squeak is legally unquestionably fully MIT licensed.

That said, unless you wear a tinfoil hat, I cannot imagine anyone seriously not using Pharo due to the above.
Do serious Smalltalk projects use version control? If so, which one?

How do they solve the apparent mismatch between Smalltalk philosophy of having everything in one image and the usual "files in directories" expected by version control?

Last time I used Smalltalk (a small project) I just kept the sources in files outside the image and reloaded from there but it felt clunky.
We are seeing more and more companies doing the transition earlier as the tooling gets more mature. But worrying about microservices before the product is not a good idea
Why this outage doesn't happen to twitter
They put the sticker on in Australia.
The backwards compatibility is for physical keyboards. So that a keyboard with just one alt can still trigger polish letters.

I don't know how other OSes allow for users to trigger "right-alt" when the keyboard has only one alt character.
Merge commits are a bit hard to understand from the perspective of "a commit is basically just a parent commit plus diff".

On the flip side, cherry-picking is hard to understand from the perspective of "a commit is basically just a snapshot, nothing more" (it's _also_ weird from the parent-commit-plus-diff perspective -- cherry-pick is kind of a weird operation, but useful enough that we keep it anyway despite it not fitting quite as cleanly into the git model as other operations).

Outside those edge cases, though, people with "snapshot" and "parent + diff" mental models will make basically identical predictions about what the results of various operations with git will be.
DNS (not necessarily this case, but man it can bring things down fast)
Here is a longer version of that:

https://www.alignmentforum.org/posts/AyNHoTWWAJ5eb99ji/anoth...
Probably an intern doing something dumb.
Is that a good idea? I don’t do embroidery but I’d guess people mix threads of different colour in the same area to merge them. As long as the image is original you can discard those areas as false positives instead of new colours; if you compress the image, that subtlety per thread is lost.
And even there, a bit contextual.

Comida recalentada is probably microwaved left-overs, not burnt scraps.
I know. XCode really doesn't compare in terms of usability, stability, range of available options, and documentation. Sad really.
This is fantastic! I think it would be helpful to be able to change key phrases just by clicking and editing, rather than having to click that arrow button. At the very least move the arrow button to the left side of the phrase.
Why does this extension need to read your browser history?
A few thoughts:

1) Hardware interface: People here are conflating hardware interfaces (e.g., on Kindles) with the data medium (e.g., paper or ebook). For serious knowledge work, such as studying, of course a large screen area (such as dual 22" monitors) and good input (such as a full-sized keyboard) are essential. I think the question is, in that environment, which data medium is better

2) Software interface: How much is an issue of basic interface design. Paper book interfaces have been perfected over centuries; ebook interfaces are still immature. With the right interface, could ebooks exceed paper?

3) Does anyone know if ebook formats combine these capabilities:

* I own the data; it's not licensed to me.

* Open formats, so the book is readable 20 years from now, including the annotations (see below)

* Annotation: I can add notes and associate them with specific locations in the text.

4) An interesting article on ebooks disrupting the college textbook business:
http://www.fastcolabs.com/3028855/why-cant-e-books-disrupt-t...
Users are not free to study and modify it to suit their purposes and fix bugs.

See here:

https://www.gnu.org/philosophy/free-sw.html
Linked site over quota. Cached:

http://webcache.googleusercontent.com/search?q=cache:tVxs2fJ...
At first I was going to agree with this statement; however, I hate carrying all of my textbooks around, and if I have the e-book of the text that means I saved a lot of money. I do love reading paper books, you cannot replace the feeling of holding a paper book in your hands. It is something that I love about paper books. But I really do love the fact that I can have all 5 of my text books in one device that weighs less than any text book I am currently carrying around.

Last semester I had all E-Books and I was able to bring them all with me at work, and I was also able to read them while sitting in my work truck in the dark. This semester I do not have any E-Books and two of my text books are fairly large. Which really sucks, because I hate having a heavy back pack.

All around I do love having E-Books, on the Kindle I can slide back and forth to different sections, high light the pages and everything I do with paper books. I also take notes on paper as I go along with the E-Book, it really helps me to remember certain parts.

I am saying this at the beginning of the semester though, I might change where I stand but I currently love E-books, except when the battery runs out I hate the thing haha. Who wouldn't love to have 6 major textbooks on one device?
Consider that Cloud Print certified printers are on store shelves and will likely be sold for the next 6+ months.
Cpus have hit their limits and not growing. Software has stagnated and recycles concepts from 50 years ago, and not growing. What's left to study? Either world-scale clouds or the growing field of NNs. Out of the two i 'd pick the 2nd cause it's either more fun or more unpredictable. Students are making a rational choice
You could also reduce the list to:

1) Root* your phone or install Froyo

2) Install ShootMe (http://www.androlib.com/android.application.com-bw-picme-loc...)

*: If you're reading this thread, and you have an Android but it isn't rooted, you're doing it wrong...
I would bet that the constituents of a West Virginia senator generally don't care about alternative currencies. They are more worried about the coal industry.
I think the problem is that many patients prefer the idea that they have a physical illness, so some doctors don't even consider emotional causes. Also, doctors simply don't have the time needed to deal with these kinds of issues.
Yes, the JIT is the problem. And no, this has absolutely nothing to do with OOP or bloated abstractions. Java is a great language, and the Jetbrains IDEs are written extremely well and have very high coding standards. It is all about the JIT. JITs do really well for code with lots of hot loops and few branches, because inlining and loop optimizations are the classic case for needing execution profiles. But IDEs are the opposite of that...there are branches everywhere, and very few hot loops. JITs are the worst possible compilation model for this type of code, because it is constantly going to be optimizing, deoptimizing, and reoptimizing code. The JIT is just constant overhead for something that should just be profiled and compiled one time.