skysight-inc/HackerNews huggingface dataset:
Clearly, a new "internet community" needs to be formed. We've got a lot of classical communities: forums, Q&A (aka: Stackoverflow), link-aggregators + comments (Hacker News, Reddit), mailing lists, IRC, Discord, Github, Wikis... to name a few.

StackOverflow is trying to build an FAQ database. The Q&A format isn't really about answering questions, its about collecting questions that are popular / drive traffic, and to focus the community efforts on those popular questions.

------

I've hypothesized before, and I'll hypothesize again, that StackOverflow needs an archival process. A long time ago, I used to play a webgame called Utopia (and its "sister" game Earth 2025)... every 6 months or so, the world would be paused indefinitely, and a "new game" would be started.

6-months is too quick for Q&A formats, but I think a rolling "pause" cycle would be great for the StackOverflow system. Every 2-years, the Q&A database would be paused, all unanswered questions would be wiped out... all solutions permanently archived as "The winner" for those years.

For example: 2010 through 2012 would be one "cycle" of StackOverflow questions / answers. The question would have to be re-asked / re-answered in the 2012 through 2014 years (and the community can "reask" important questions every 2 years to ensure their continued communication).

The cycle of life / death of questions has caused the StackOverflow database to become too large. I think it needs to be archived, torn down, and rebirthed every few years. Its too much to expect an answer from 2012 to really remain relevant today in 2019.

Its too much to expect newbies, today in 2019, to know that some question was answered in 2010. Its too much to expect old moderators to comb through old questions and "update" wiki answers with information in 2019 to "fix" problems from 2010.

Case in point: modern compilers use cmov and avoid the branch-prediction question. This question is no longer relevant on modern compilers: https://stackoverflow.com/questions/11227809/why-is-processi...

Yes, its important and tells an important tale about how compilers worked back in 2012, and yes it should be archived. But time has moved on, the world is different now and the Q&A Database is failing to keep up with the changes.
Interesting how everyone ignored the point you made about the homelessness in SF.
I release two apps, across 3 OSes, in somewhat of a bimonthly cadence with a low defect rate. That’s 6 different binaries. I’m a solo founder.

I know people like to rag on Electron, but without it, I wouldn’t be using something else, my apps just wouldn’t exist. It allows more people to try building more thing and that is a net positive.

The speed problems and bloat issues of Electron is just shoddy programming on the maker’s part - Electron itself isn’t slow. I use it largely as a shell talking to a Go binary that ships within the app package, which makes it only tasked with UI. If you’re having issues with speed, it’s a good approach.

A real world example of this approach is the thing I work on at https://aether.app. (An async collaboration tool for engineers)
There isn't too much to the rendered document, it reads the text as TSV and breaks that out into rows and cells. I tried keeping it as simple as possible for now, the idea isn't to help analyze data, but be able to share data in a usable format easily.
So is "not stupid" also an unnecessary start to an answer?
I wouldn't mind the homework interviews if they paid me to take them. In fact, on-sites should be paid also.
Actually, getting to 90-th percentile of public speaking and self-presentation make you little bit of celebrity regardless of any other factors.
Income is the real deal. Point is people want to be able to afford normal things like housing, medical care and some good education for their children.

I don't see this as problematic that Buffett sits on hundreds of billions. But the fact that 150k annual income qualifies for subsidized housing in SF - well that's ridiculous.
I had a teacher in the University who took some courses taught by Feynman and had the same experience. He even tried to record some of the lectures, but the result was similar. While he was listening, he felt like everything was very clear. But as soon as he stopped the tape, nothing made sense anymore.
As an ignorant and neutral bystander, I’m really curious why this is downvoted and would be interested in reading the rebuttal (seems like I could learn something).
Ask HN: Is it still feasible to learn Ruby / Rails in late 2019
A bit of context first: I was a PHP developer up to 2014, when I moved into management roles. Since then, I did a bit of Node (I personally don’t like it) but nothing else. Back in my PHP days Rails was all the hype (I guess that’s gone now?) and I wanted to learn it, but never got the time.

I am now at a crossroads, I’m fed up with management and want to transition back to development over the next 2 years. I can devote 1-2 hrs/day to learning something new. End goal is to work on small to mid sized projects in the SaaS space.

Now, every time I look at Ruby, it feels daunting because the language is quite big. Rails is even bigger. What bums me down really is that there are folks who have been doing Rails for 10+ years and I’m only starting, so job opportunities don’t look promising. Also, Rails evolved so much, a lot of tutorials are out of date, as are gems, plugins etc.

So, given all of this, what would be your take, or alternative to learn? (With the hopes of working with that tech full time in 2022)
>Apply separation of concerns properly

With the component paradigm, these things can't always easily be separated. Or, it is useful to consolidate data concerns and UI concerns, but often data concerns like UI have a hierarchy, or the concerns are spread all over the place (not in neat, clear groups).

It is very useful to declaratively specify the recipe for both UI and data, and allow the framework to coordinate these things across and within components.

>Rendering should never need to be interrupted.

Following this line of thought would lead to not rendering anything until everything is ready. Large applications have multiple levels of components and data concerns. These solutions allow for isolating responsibilities at smaller levels, and coordinating their presentation in ways that produce good UI (few loading spinners, flickering etc).

>and if limited to that use

This simply passes the responsibility somewhere else no? And any significant apps can't avoid these concerns. You'd still be left with the coordination between React and whatever else was handling these concerns, but with much more code likely to tie them together.
Inner centromere: biomolecular condensate on chromosomal passenger complex
That sounds like a common idea the Dilbert author mentions from time to time.

He could draw a little, and he knew about the business world a little, but not many people could combine those things -- and be a business cartoonist.
Getting Visibility Across Cloud Environments
Should have passed an A/B test on your headline with a focus group. Everything with all the Facebook privacy issues it's getting much harder to push tracking on the technically literate.

I personally don't care if your hosted one takes telemetry as but if it ever makes it to CE I'm dropping gitlab in favor of I guess paying for some other hosted service. That or I'll patch out the telemetry.
Poland is experiencing rapid growth in car ownership because people are getting wealthier and can afford cars and gas, while public transportation outside of dense cities is slow, inconvenient, expensive, or all of the above.
I see more and more people moving to Slack communities for the QA that they used to post on SO. This is sad - slack is a closed protocol and is not searchable. Answers are only available to a subset of the tech community and only for a limited time (no one really searches before asking the same question again but someone will usually prompt with "that got asked a couple of days ago" in cases of extreme duplication.)

Spectrum [0] is heading in the right direction to counter this but it's still a walled garden.

[0] https://blog.apollographql.com/goodbye-slack-hello-spectrum-...
It's also caused by hepatitis (B and C)[1] which effects millions of people in the US[2].

1: https://en.wikipedia.org/wiki/Cirrhosis#Causes

2: https://www.cdc.gov/hepatitis/hcv/cfaq.htm#statistics
Oh I didn't read the "preview" part, that's why I was surprised with all the uBlock issues. Thanks for the explanation.
This isn't really true. Electron itself has a renderer process and a background process. It's completely possible to make multiple renderers with independent windows that can coordinate with IPC through the background process. We have an electron app that does this and has undockable tabs, it's not even very hard to implement if you're using something like Redux for a window level state store, you just pass it thru IPC to the new session.
When you learn Spanish read next (in this order) Cortázar, Onetti and Carpentier.
Everything you've said is true of the world we're living in, but they aren't inherent natural laws - our changing culture has devalued employees to the point where they are viewed as having as much of a say as a building, but it's good (while accepting this is the case) to question if it must be the case and consider how else things could work. Given more ownership of the ultimate ends of their labour people are more invested, this is why key employees are often upgraded from mere tools to investors by the issuance of stock options - that sort of thing is never going to happen in a company like Boeing merely because of our culture.

If Boeing had granted partial corporate ownership to technical employees they would advocate much harder for the caution that could have averted this incident, bonuses (and the mere promises of such) are a partial salve to this but have other complications around being non-binding, unaccountable and a form of wage insecurity.

So, I just wanted to mention that this sort of creeping failure isn't inevitable, it's inevitable in the scenario as presented. Given a different company culture this incident likely never would have occurred and giving employees and vested (and vesting HA!) interest in the company is one such route.
they cooperate and steal from you
This is morosely funny, because the responsible community viewpoint has been tilting at windmills for over a decade about the pitfalls of centralizing webcrapps. Which has been ignored due to a blindspot from just being subservient to US business interests, as so much of US culture is.

But now that China has appeared on the scene with a modicum of influence, everyone flips their shit! For some reason people couldn't just reason abstractly about the implications of centralized control, but instead assumed the controllers will be benevolent up until they became "too foreign".

I don't look forward to the likely results though. I think it's going to be more top-down control from DC to SV (it's the only thing they understand, after all), as opposed to any sort of movement to get back to making secure software rather than untrustable services.
> "the problem really is drivers most of the time it's not something you as a pedestrian can do anything to mitigate or prevent.

Of course drivers are to blame, but that doesn't mean there aren't things pedestrians can do to improve our odds. My point was never that drivers aren't to blame. If I had a magical wand I could wave that vaporized all cars, I'd wave it and solve the problem for good. But I don't have that and fantasizing about it won't help me. What I do have is the ability to, for example, establish eye contact with the driver of every car I step in front of.

Will that keep me safe? No. Will that make me safer? Yeah, I'm pretty sure it does.

> When running I wear reflective gear and headphones that allow outside noise in so that I can hear the road, I stay off the road in pinch points or areas of the visibility, and I still got hit when being careful."

Did you stop wearing reflective gear because of that? Probably not, because I'm sure you do actually recognize that reflective gear makes you safer even if it doesn't make you safe. That's all I've been saying. If somebody comes at you with homicidal intent, reflectors won't help [you]. But if a driver were lazy, inattentive, tired, or otherwise dangerously incompetent but lacking murderous intent, there are many things a pedestrian can do improve their odds. Or maybe you want to believe that every single driver has murderous intent and reflectors are a liability to pedestrians because they make you easier to hit, but I'm pretty sure that's not true. Supposing it were true though, the pedestrian could still opt to camouflage themselves by wearing dark clothing with poor visibility....

Just to reiterate: The possibility of the pedestrian taking defensive action does not in any way suggest that the pedestrian is at fault when they get struck.
One step at a time. And if that doesn't work, then you find another team ;)
Why not?

Pay your engineers 500k in a medium cost of living city and you will have the best employee retention of any company once they get used to their quality of life.
I loved Flash for those things. However, a majority of my interactions were websites for things like restaurants where I couldn't copy/paste basic things like the address, didn't have progressive loading, search, bookmarks, scrolling and the performance was abysmal. Flash could technically do all of those things, but never happened in practice.

html5 was supposed to bring all the cool things Flash had without most of the annoying things I mentioned above. I saw some cool tech demos years ago, but for whatever reason (lack of good artist tools?) I haven't really seen much in years.
Atomic-scale fragmentation of antiferromagnetic order in doped Mott insulator
Proposal: Scaling the Go Page Allocator
This is broadly true, but humidity has a huge effect which I think parent was alluding to.

Coastal mist at 5 degrees isn't remotely comfortable to hike in with the clothing you describe, unless perhaps you are trail running.

What's that old line about the worst winter someone experienced being a summer in San Francisco?
I am huge React fan, but when I see how complicated are some of the modern React codebases in some "leading" companies I have a strong feeling that we will soon need to go back to drawing board and hit some kind of reset button. As I said, I love React ecosystem, but there is something fundamentally wrong with most front-end developers today. They build bigger and bigger SPAs because they are confident that React ecosystem makes it maintainable, well good luck maintaing React/Redux/Graphql/hooks/bazillion-libs after 5 years. Abstraction is good, but it has its limits.
Is the Putin era waning? Seems like it might still be deepening.
Then maybe they should pay for social services, instead of pushing their problems to someone else's porch.

Also, I'm not sure the set of people that this sub-thread has been railing against (Hipsters who smoke weed, and are hypocrites for tolerating the homeless, while pushing them around) has much intersection with the demographic you described!
It's not hard - just build more housing. Prop 13 and local politics make this so much harder than necessary.
Sure it is. People are very set in their ways of using computers. Not to mention they are on opposite ends of the Alphabet so also the list. The other link posted here about the guy who had never used it, he didnt explore, just froze when something wasnt familiar.
The triads get "get outa jail free cards" in return. Imagine the incentive they got...
"controlled inputs" are certainly the recommended React idiomatic pattern, but you can use standard uncontrolled inputs if you want.
Not him but I also leave my iPhone wide open.

I primarily use it as a camera and tape recorder. And mobile wifi web browser with retina resolution in rare cases, all in which I specifically avoid using it to use any sites that require logging in.

I have a fake name on it. There are no contacts or email accounts set up on it.

It's not ever been activated as a cell phone.

Basically, I see no reason to have a password on it, and a password slows things down slightly and has the risk of forgetting (since I never reuse passwords), so why bother.

My Android phone that I do use as a cell phone though I have a password on it. It has similarly few personal details, but the call logs would make it easy to identify me.

Granted the iPhone's location logging though disabled might be storing info anyway, and probably the photos are GPS tagged, so those things would identify me.
Simple carbs?
Because 4 or 5 years of real world React development have proven them inadequate suggestions.

React itself was created in opposition to arbitrary separation of concerns dogma. The concern is the component, the entity encompassing both UI and data manipulation code, as well as styling. Separating all of these parts into isolation does not result in more maintainable code or better UX.
I wonder how two different teams can be so different in culture saying they do the same thing. My team looks at velocity only as an indicator of how much we think we can reasonably take on looking ahead and as a warning sign if things are falling apart.
When I dont find anything on the web I go to IRC. It can take some time to get an answer so in the meantime I go to other channels and answer questions or just hang out participating in interesting discussions.
You should start looking for another job, your management is obviously toxic and incompetent.
It used to be that the "profit" from advertisement paid for journalists to write stories that would get you to look at them.

Now the profit from ads largely goes to engineers to build products for the web, (and shareholders of tech companies).

Both journalism and web stuff provide public good, but we need to figure out how to replace the revenue that financed journalism. The public was getting it for "free" before, and when it moved online we continued to want to get it for free, but the advertising model did not survive the transition.
Unrelated, but do people on HN have a different definition for the word "trivial?" It's used so frequently that I wanted some clarity.

Where I come from, trivial means "of little importance," ex: The Kardashians' drama is frequently over trivial matters.
Why send user data to third party ? Don't they have the man power to build a db with all the logs and maybe add that to a securing ml bullshit for Enterprise ?
Some of us are less sensitive to it than others. In particular I am prone to migraines in bright conditions, and on a bright summer day I have difficulty looking at the sky, which will be coated in thousands of bright and distracting microscopic floaters *

* https://en.wikipedia.org/wiki/Blue_field_entoptic_phenomenon

And yes, I'm offering anecdotal data-- but I've already provided the relevant studies so this is just a bonus. In my case, the slightest thing will keep me from sleeping. My A/C was out last night and I got scarcely and hour of sleep because of the heat. I am manic depressive and sometimes I will stay up for days if I don't make extra effort to fall asleep. f.lux particularly made a very noticeable difference to me within days of adopting it.
Datetimes are easily in the top ten most annoying parts of programming.
This is not correct. Apple's page explaining their iCloud encryption states that they use end-to-end encryption only for a few specific types of data, and only if you enable two factor authentication. iMessage in particular explicitly sends its encryption keys to iCloud (so that iCloud can unlock your messages if you lose your device, but of course this means iCloud can unlock your messages for any other reason without your knowledge). https://support.apple.com/en-us/HT202303
There's nothing inherently special about rendering. If the function is an unresolved promise then it should automatically await, and treat that component as blank or nonexistent. It's just legacy architecture to make render functions sync and blocking.
> There is grey area where people under economic duress are taken advantage of and will ‘consent’ even if it’s unpalatable to them, if they had alternatives.

I don't see how this is any different than taking any other menial, low paying job because you have to make ends meet. No one really wants to clean public toilets or work at Wendy's.
You might want to go tell Justin Trudeau that.

Oh yeah, it’s not an issue if the candidate we like won.
“RoboTrump” AI Mimics the President’s Writing Style
Interviewing generally has a significantly negative impact on your mental health... but at least it's temporary.
not exactly the most performant but there is https://ultralig.ht/
Game Programming Vexations: The Problem with Libraries
very insightful, thank you
Because if you're not the customer you're the product. For-profit publishers have abused the reader-pays model into disrepute, but author-pays and sponsor-pays is an awful way to run a journal.
How did I misspell "blindfolds" twice!
I want to call BS on the statement "Most meetings can be replaced with documentation." Maybe in an ideal world, but no.

Have you tried reading the documentation the average engineer makes? It's like a freshman essay -- lacking in cohesion, vision, context. It's usually completely unstandardized across teams.

And 9 times out of 10 the most fundamental questions aren't answered by the documentation e.g. "Why don't we just use existing tool X to solve this problem?"

Communication is hard. Engineers use buzzwords. Product uses buzzwords. Companies use buzzwords. Combine all these and you get a soup of overloaded terms e.g. "service," "connect," "access," "resource," "platform" that have a wide range of potential meanings.
Microsoft is still considered a pariah by the kinds of people who would use gitlab.

It will be 100 years before my company puts their core business in the hands of a SaaS provider.
>Insert any framework in place of SwiftUI. You're describing Qt, essentially.

Only Qt never had the funding or resources or will to get native UI right.

Their non-native widgets are always off, in a way that even Electron, is not (because it being web-based means it at least follows familiar conventions for all web users, where a mimicked native GUI enters the uncanny valley).

There are also custom native but not platform-native (meaning close to the metal, no web-based) GUIs like Adobes, Fruity Loops, and others, that look good on all platforms and users have no issues with them.
Async work is but a tool, a methodology, remote is a way of life/work. I advocated async work when working office-based as well, the same principles still apply.
My general lean here has been to use a library like redux-first-router (https://github.com/faceyspacey/redux-first-router) to have this data lookup stuff happen based on routing and existing Redux state, and conditional rendering wrapping for specific components using that data (for example, https://github.com/acdlite/recompose/blob/master/docs/API.md...).
Stop being obtuse. And stop banging about Europe and phones. You blatantly haven’t got a clue.
It’s not “on prem” anymore when part of the product is on a third party server.
An interesting backstory on the 27th: https://en.wikipedia.org/wiki/Salary_Grab_Act

Politicians never change! They've gotten better at this trick by making the bills 1000 pages long, while adding last minute changes.
Letters to Penthouse, NRA Edition