skysight-inc/HackerNews huggingface dataset:
There are some things I really like about this, and some things that can shoot you in the foot.

Like:

- Having more than one component in a file. A lot of complex components can be made simpler by breaking then into many smaller, temper components. A lot of these helper components are too specific to warrant generalized use. Adding a new file for each one (especially if they're only 3-5 lines of code) clutters the code base, so keeping them in the same time where they're used makes sense. You can always pull them into a separate file later.

- Not making everything "index.js". That really makes it more difficult to keep track of what's what code is where.

Dislike:

- using indeed.js for experts. This makes it easier to accidentally add circular imports, and much harder to track them down.

- putting all components in a components/ directory. This is fine for smaller apps, but it starts to get unweildy once you add more features, teams, or team members to the repo. This is especially true if you use redux, Apollo, and React-router (or any of their competing libraries). Selectors, reducers, GraphQL queries, get spread across the code base, and it becomes difficult to teach down which component rely on what selectors (for example). This starts to bog down onboarding and cross team collaboration since ownership becomes more difficult to define. You end up with spaghetti code pretty easily.
Ukrainians Are Using the Quiet Resistance Tools They Need
So are we permanently going to be on "{Eastern,Central,Mountain,Pacific} Daylight Time"? Or are we redefining the time zones "{Eastern,Central,Mountain,Pacific} Standard Time"?
Hot take: permenant daylight time not permanent standard time because nightowls are more common than they used to be.
Those billions of dollars of R&D explicitly went into preventing you from organizing your subscription - since at scale that probably leads to more "engagement".
"There are a couple of types of flaky tests that come to mind:

Tests that perform network operations
...
The first one is easy, ban these. You don’t need them in the blocking portion of your pipelines."

At a certain large FAANG company I worked at in the past, there were some end-to-end tests that used the network that were blocking. Most e2e tests were not blocking, but a few were considered critical enough to halt the whole build/deploy.

We had a system that checked both flakiness and running time for each of these tests. If they were consistently flaky, they were removed from the pool and the owner was informed and had to manually work to put it back in the pool and get sign-off, including showing things like load test results to prove that the same test had been run many hundreds of times in different environments.

"Your version control system not being able to handle the sheer number of references and operations done to the repo."

This was also an issue. For most companies, git is totally fine (unless you are filling it with petabytes of binary data or something else that is not a good idea without special mitigations) but the argument that "git is used by the Linux kernel! It should work for you!" falls down when your codebase is at least 20 times bigger than the Linux kernel.
Those AVX instructions use more power at least in part because they massively better utilize the silicon, so you're making a tradeoff between speed and efficiency as per usual.
but it's true...
I'm actively looking for a house and it's not the prices that bother me the most. Sure they're higher than I see them but they don't necessarily feel so high that it's a bubble economy. The real thing that bothers me is the extremely high property taxes in a lot of areas. When your monthly property tax is 50% or more of your monthly mortgage payment that is ridiculous. There is no dream of home ownership if the tax man just can come steal it out from underneath you.
Oh, we've changed them so many times at this point. In the 2000s we changed the dates that we move the clocks back and forth.

This is probably just a configuration update.
US Senate approves bill that would make Daylight Savings Time permanent in 2023
> They are better utilized in smaller or failing companies that need the advantage of the boost.

... And why would they do that? Smaller companies often can't pay the same and failing companies are mental health events waiting to happen. Most people leverage their experience and effectiveness into a better bargaining position.

Also why are you thinking that labor is zero-sum? Most developed countries these days have lots of jobs that are zero-sum, but software is definitely not one of them. There's a voracious demand for software developers all across the skill spectrum.
Does the house need to pass it? Will the president veto it? When can I literally set my clock to this?
That act refers only to the ICC, which is not a sovereign state and only prosecutes cases that the sovereign states are themselves unwilling to prosecute.
True, but this keeps daylight savings permanent not standard time.
I suspect GP may have astigmatism. A girlfriend of mine had it and constantly would complain about my devices being in dark mode whenever she had to use them. She eventually showed me an article on how it does actually make text harder to focus on for them.

https://medium.com/@h_locke/why-dark-mode-causes-more-access...
Nothing these days sounds more like virtue signaling than calling things out as virtue signaling.
> Basically the Go community got the exchange off on the wrong foot.

Indeed. Then there was that whole controversy over the naming collision with the Go! language. Basically there's an unspoken etiquette in the PL community that there should be zero name conflicts between languages, as there are enough good names out there, it really shouldn't be an issue. The Go! language had been around for a long time, and I realize it was an obscure, little known language, but that's true for 99% of languages out there. So the idea that Google can just invent a language out of the blue with the same name as yours, after you've been using the name for a decade, and then just use their size and clout to essentially destroy your language is.... well that's unsettling to people in the PL community. The way they handled the situation didn't exactly win over hearts:

The naming similarity is unfortunate. However, there are many computing products and services named Go. In the 11 months since our release, there has been minimal confusion of the two languages, so we are closing this issue. Status changed to Unfortunate.

https://github.com/golang/go/issues/9#issuecomment-66047478

Basically a sad trombone. The image of Go has never recovered in my eye.
Partly, yes.

It is echoes of the respect one human has for another.
Move it all twelve hours back forever, then we'll have eternal daylight!
Although the specific list of topics may be up for debate, I completely agree that software engineering courses are all very theoretical. A degree in CS barely prepares you to be successful in the industry - instead it exposes you to a wide range of topics and skills out of which only a few may be valuable for each individual.
I've only worked in PHP once, in college, so take the following with whatever level of credibility you wish. I generally work in infosec related projects that often come at strange intersections, such as embedded systems and web applications or real time operating systems in safety critical situations which must deal with data from unreliable or weakly secured sources (802.11, LoRa etc.) So, mostly my experience with Go is the need to write one-off tools, which usually provide either a CLI or web-ui, to inspect things embedded devices are doing as a sort of "black box."

I'm sure generics are going to be useful in some instances. Also of note 1.18 is bringing built in fuzzing, which is nice.

Where I'm getting my margin of benefit over writing tooling in say Python or Ruby, or other languages that fit this domain:

1. Fewer choices: The build system, module layout, and networking APIs don't lead me down the road of trying to figure out which library is best, thereby wasting time learning different libraries. I have never had any desire to google around for external libraries etc. Everything seems to just work fine.

2. Clear design intent: Once you've figured out what you're supposed to do with language idioms, like passing around ReadClosers or whatever it becomes super easy to read code written by other people who've also come to understand the intent. I don't notice this until I try to go back to doing something in Python and remember how vastly many approaches folks take to the same problem (like how should a database object be passed around.)

3. Works for my workflow: I spend most of my life in terminals fussing with serial communication, or fighting with mqtt or an APK that won't load like I expect, etc. The tooling with Go for nvim is incredible. I've found that now that I've gotten fairly fluent in the language I will often crack off small scripts in Go to automate dumb things I don't want to do in Bash or whatever, this is maybe an anti-pattern, depending on who you talk to.

Summary: My big margin over other languages just comes from consistency of design and interfaces and the fact that Go integrates with my workflow. It's very easy to figure out how to do a thing the first time I'm working on it. It's also easy to throw together a one off tool in an afternoon, use it for two weeks, push it up to my github and forget I did it until the next time I need it.

YMMV
Such a terrible idea compared to permanent standard time.

There is plenty of light during the summer, so there's no need to optimize for that. The winter is when daylight is scarce, so that's what should be optimized for.
> It seems to me that the intensity with which some people fixated on the absence of generics cannot be explained just by frustration with writing non-generic code, which by all accounts was annoying but not overwhelmingly so.

You speak for yourself here! Miles of copy pasted code, slightly altered who knows how, impossible to refactor without either using code generation or eschewing type safety altogether was my experience. Its impossible to write entire classes of general purpose libraries with type safety! Its just beyond belief to me that "copy paste" is an actual, bona fide best practice in the community, or that a 'map' function is unexpressible!

> There's also a bit of an anti-expertise "who are you, Go creators, to say you know better than me how to design this program/engage in software development?"

Go the compiler/runtime is super impressive! Cross compiling small, binaries with a switch is awesome, so kudos! Go, the language, on the other hand, sucks; it actually sucks so much, that historically, we couldn't even write libraries to work around the things that suck. That is frustrating!
I did one in C a while ago if anyone is interested:
https://github.com/glouw/gel
More of the same problem of too many developers feeling they control my computer.

Removing something from new installs is rather different than removing something from existing installs.

The future of browsers and search engines sure has been a disappointment.
Looking forward to the boost of crop production with the extra hour of daylight!
I think this form of protest is outdated in modern times.

We're constantly being bombarded by war footage, dead kids from school shootings, suicide bombings, and collapsing skyscrapers.

This may have been significant back in the day but now it's hardly a blip on the radar of tragedies of people trying to send a message through violence.

I personally find it to be a sad senseless outdated cultural practice , no matter what the message is.

I find absolutely nothing powerful about killing oneself without taking a whole bunch of your enemies out at the same time.
Figured it's worth mentioning that none of those are in the top 10 of highest accident rates per vehicle. Agreed performance != accident prone.
I think it's at least partially about value vs (mutable) reference semantics in Golang's case and the hope is that the compiler will know to whether heap or stack allocate based on escape analysis.
Of course they do want the independence, why would they not. It's just that after decades of occupation and China's economic rise, they feel that that is an impossible goal, at least until China implodes like the USSR did - which may or may not ever happen.

So, they are asking for the next best option as a compromise - even the proposal is called middle-way for it is a compromise.
A more robust type system can help you deal with coordination between various nooks of a codebase.

For example, let's say our platform supports multiple authentication methods. If we need to add a new auth method, how do we know all the spots we need to update? TypeScript can handle this using a sum type:

type AuthMethods = "push" | "sms" | "fancy_new_thing"

// No errors
const authMethodHandlers: {[key in AuthMethods]: CallableFunction} = {
push: () => {},
sms: () => {},
fancy_new_thing: () => {},
}

// Error: Property 'fancy_new_thing' is missing
const authMethodTitles: {[key in AuthMethods]: string} = {
push: "Push",
sms: "SMS",
}

With the above approach, static analysis tells us when we missed a spot. That adds a ton of safety and expedites feature work (since engineers don't need to manually find all the spots that need updating).
I prefer having more daylight in the evening. I never really understood the opposite argument.
Now Go has everything I need in a programming language!
In dictatorship like russia, it is hard to believe that you can easily interrupt a live stream by standing behind a news anchor and nobody stops you (do not forget that this is the main TV channel in russia)
Secondly, the majority of people that work on TV say that live news is not really live, there is always a slight delay to avoid anything unexpected going live (but not in this case). Thirdly, 280$ fine while others facing 15 years in jail?

Seems like yet another masquerade created by Russian propaganda.
This comment has the tone of being genuinely inquisitive, yet it mostly comes up with negative and depraved reasons for as to why someone one might dislike $lang.

- Rational reasons (frustrations with the language design) are briefly acknowledged but then some reason left by the wayside

- It is suggested that people don't have principled objections to $lang; they will "latch onto" something else if $misfeature is fixed

- Simplicity, a universally praised quality, might be the problem

- ... Because it can "humiliate" someone who has wasted time on needless complexity

- "$lang has opinions", which all languages have whether they acknowledge them or not. Why should this bug people especially when it comes to $lang?

- "Anti-expertise" for some reason, even though creating any "enterprise-ready" language takes expertise and many years of effort. (This also seems to be at odds with the "anti-simplicity" point?)

- ... But aren't then people who argue for $lang also anti-expertise? They are after all taking a stance on something that they are not experts at; they should take a neutral stance and defer to the experts

I would say that it is rude to suggest that someone might not really be arguing against X and instead ask what they are really upset about, since the follow-up questions and implications are absolutely never flattering. They inevitably just dive into the gutter with suggestions like "maybe simplicity humiliates you".
PSA: If you use Google Domains to buy a domain for your company DO NOT USE IT TO ALSO BUY GOOGLE APPS (or whatever it's called this month).

If you ever want to change your company's primary domain... you can't. We're stuck now with a legacy domain (configured with an alias so it's invisible to others) that we can't move off of without basically burning the whole thing down and starting fresh. It reeks of technical debt and poor engineering design that buying Google Apps through a reseller (where that reseller is _also_ Google) totally ties your hands for properly managing your deployment.
Huge win for solar power.
this is the first time ive felt something in weeks
Honestly don’t even care at this point, would take either way to end this nonsense.
When it’s scarce you want to waste it on the early morning?
This brings me back. In the late '90's, I interned at Sun Microsystems with the team responsible for the ISDN infrastructure that enabled people to work from home. My job was to automate modem SW upgrades for modems in racks in data centers and for remote users. The latter group was more challenging to serve since the upgrade could only run when they were connected and and "breaking" something killed their internet connection - it happened a couple times :(
I would expect that projects that are rapidly growing and profitable to be relatively safe from Google's we-don't-wanna-do-this-anymore hammer.
Which production-ready datetime library doesn't use zoneinfo? There should be no need to patch otherwise there would be quite a lot of patching happening each year. The current version is 2021e, meaning it's the 5th iteration for 2021.

Notably Fiji decided to not use DST in 2021/2022 but apparently plans to resume using it afterwards.
Thanks, I'll be in touch.
Might also want to note :cq[uit] to quit with an error code. This can often be useful when you're using vim as your $EDITOR and wish to tell the calling process that you want to abort.
This would give us an "extra hour" of sunlight in the evening during the winter.
have bought few domains with them, seems pretty basic but works
>probably just a configuration update.

famous last words
That's HN for you. I honestly don't know why I keep coming here.

This is a safe space for rationalisation, we can't let 'the feels' creep in and threaten that.

Also it would be way too 'political' if we assigned a moral valence to torture, and political discussions are discouraged here.
Perhaps the trouble is when you encounter other peoples abstractions, or when you return to abstractions you’ve long since discarded :)
I lived in Dharamshala (home to the Dalai Lama and the Tibetan government-in-exile) for 3 months a few years ago. My partner at the time went back to the US to visit family, and I didn't want to leave Asia so I went there since I had some interest in Buddhism at the time, too.

In random book stores, I met actual monks who had served time (in China) as political prisoners. One of which had also written a book about it. It was kind of funny to walk in into a book store, see these two guys drinking tea and then get pulled into a conversation out of curiosity. But, as for the stories themselves, probably not that funny. Some of the people (monks, mostly) had physical scars and their stories were anything but fun.

I also went to their offices (a modest distance away from the Dalai Lama temple, but very walkable) and got to speak to senior officials there. I asked them basics questions like, "What do you think is the future for Tibet?" and they were very accommodating.

We had tea, laughed and talked life. At first they thought I was a journalist, which was hilarious since my approach was very blunt but curious at the same time.
The zoneinfo files describe the rules, past, present and future
> How far we've come. I remember having a semi-decent on board 100mbps LAN was only reserved for highest end.

These cpus are much more than 10x faster than the CPUs you would have used then.

Networking speeds in desktop devices haven't kept pace. Not just with cpu speeds but with storage speeds-- which is particularly obnoxious when you want to use network attached storage.

I assume this is due to a mixture of internet and wireless creating an extremely low bandwidth least common denominator and that running >1GB over copper is kinda problematic (finicky, power hungry, etc) -- and the industry seems to reason (perhaps correctly) the the customers in this segment can't handle fiber.

I personally have 40GBE attached desktops (and 100gbe attached stuff within the server rack)-- thankfully quite economically due to surplus enterprise hardware, so I'm well aware that it can be done... but to do it in a small formfactor system is still a problem, e.g. for any of these non-apu systems your normal mini itx systems will use all their slot space for a graphics card and not have room for a mellanox adapter.
My usecase is something alone the lines of building a product/hosting solution that allows users to place files on their drive and I'd modify/sync/hotlink it to a cloud hosting server. Amazon Drive seems a good candidate too, I'm simply looking for the most popular one that users use and one that has decent API support for download/uploads.
The right not to be tortured and the right to not be murdered (by the state or anyone else) are practically uttered in the same breath.

You can't fix violence with more violence, you have to fix violence with cleverness.
Can you explain to me why this is good. It seems like a pain, but I assume there must be a good reason for it. Does it truly save energy? Is this documented somewhere?
I lived very close to there and drove by the location every day. It is on a very busy street where you would never imagine that something like this would have happened. It wasn't until a local pointed it out to me that I realized what it was. The monument is beautiful.

https://goo.gl/maps/k2dsRfHeNXYW2My2A
Really? Seems pretty straight forward. For early risers it's nice to wake up to the sun...

I think it comes down to, "what do I prefer"
Dynamic Programming in Python (2016)
They're backed by the same registrar, so it makes sense.

Disc. Googler, not in Domains.
And Corfu was written by the same person as this OpenStreetMap Viewer.
The fact that another thread sees the incremented value implies that that thread will see all stores that happened-before that incremented value.

A fence or atomic operation guarantee that a store will be visible globally in a finite amount of time

Edit: that's true for C11 _Atomic as well (I had to double check), I.e. x++ if x is an _Atomic int is both atomic and seqcst
Let's not be hasty; we could use math to accelerate time itself. Right? Right??
I'm seeing a free-parking lot (with EV-chargers to boot), "Ava's Downtown Market & Deli", a barber shop.

Those three things alone are sufficient to make one bus-trip from this location per week worthwile (free parking near a bus-stop that takes you to the doorsteps of work). At least, whenever you get your hair cut, and whenever you need to buy more higher-quality salami/cheese from the Deli for your home sandwich preparations (and whatever else that market keeps in stock).

I don't live there. I don't know everything that Mountain View has to offer. Maybe there's something else there that's worthwhile for lifestyle: a gym, workout center, arcade, bookstore/library, etc. etc. I think I see a dance center (maybe you're not a dancer), but that suggests that some kind of workout culture is in the area, so maybe there is a gym there that matches your activity style (or maybe you can learn dance as your activity to take advantage of that location)

--------

So already, the home -> free mountain view parking lot -> bus -> work -> bus -> parking lot -> home trip seems to have been proven reasonable.

There's also a CVS on that bus-route, and seems to be walking-distance from the free parking lot as well for other lifestyle shopping needs. This doesn't seem unreasonable to me at all.

There's also the occasional needs items: the post office and a few banks.
I think you could get 99% of the value of an overlay as a simple fold or map over the result. Introducing the second argument feels very much like a workaround to allow you to avoid the infinite loop.
Serious question - dedicated servers/VPSes with unmetered bandwidth are still a thing. Get a few of those, point your DNS name at all of them (for redundancy & load balancing) and rsync/FTP your files to all of them.

I can see this being a problem with viral, publicly-available content, but for subscription-only content the traffic patterns should be relatively predictable and capped.

Am I missing something?