skysight-inc/HackerNews huggingface dataset:
And I'm in the rocky mountains in Canada, where basically everyone says "Solar will never work here".

In my experience, solar works everywhere. TONS of friends in Alaska and Yukon have been off grid since ~2010.
Typically no. It's a different career path. They would start as the low guy in a big kitchen, probably go to culinary school as well, like this article is talking about.
Even cheaper are esp32 boards. Seeed has tiny esp32c3 with camera included for $14 USD. Granted the camera module isn't the greatest but it may be good enough for sky tracking, there are also other camera modules.

I feel like RPis are overkill unless the data is being processed in situ (even then the rpi may be overkill compute) beyond just packaging it up digestibly to be crunched elsewhere.
I clicked around a little and I think that the correct page for me is this one, perhaps it is the correct one for you too? The script doesn't work, but it looks like it could work with some tweaking. https://www.facebook.com/adpreferences/ad_settings/?section=...
Though if we're going to make implicit-limit buffet comparisons, 5TB isn't even enough to mirror one hard drive. And the better comparison to what used to be unlimited is the "business standard" plan which only allows 2TB. That's a lot stricter than simply stopping "abuse" of the unlimited storage.
SSH as a Sudo Replacement
Smart people with strong opinions. What can you do.

I've come from a merge workflow into a rebase (git + gerrit) workflow in a huge software project with hundreds of people. Rebase workflows are fine. Merge workflows can be fine.

Personal preferences + the way you're used to doing things.

There's some advantages to being able to see how conflicts were resolved when you're looking for something that went wrong but if you have code reviews and tests then the probability of needing that in a rebase workflow is smaller. In a large team "how we got to a change" is IMO less interesting than "this is the change".

Have seen occasional breaks from things that were incorrectly rebased (generally from auto-rebase situations), but those are rare enough and easy to address. Same things can happen with merges.

An IMO much larger question is branching strategy. Normally if you're following a rebase workflow you're doing trunk based development. Many teams that use a merge workflow use feature branches. If you use feature branches you're pushed towards merge workflows. That's a bigger debate maybe (and I'd vote for trunk based).
Our team switched over to Graphite [1] 8 months ago now. Graphite involves a lot of "restacking" (i.e., rebasing for every commit/branch in a "stack").

No one on our team had used rebasing extensively before this, but it's hard to go back. Similar to the article, the benefits we see are:

- Fast iteration with `gt m` (`git commit --amend`) and `gt s` (`git push --force`)
- Using `gt restack` (`git rebase` on each parent commit) helps make merge conflicts more transparent in what happened
- Commit histories are much more legible

I highly recommend giving it a go.

[1] https://graphite.dev/
I'm experienced with both sides here. I think they're fairly comparable in moves/complexity if you include the non-partnered dances in general.
This particular development is probably good. The problem is the invisible graveyard of all the other good things that never happened.
Try Fedora 40. If you love MacOS I would say you would enjoy the latest Gnome
One of their three. HI3 and HSR aren't the same game.
A friend in Bulgaria had a similar size CRT in his house when it got burglarized. The burglars drugged the dog, disabled the alarm system and stole all the things, except for the giant TV (they couldn’t lift it).
Here's another exponential trend. It's showing no sign of slowing down, despite the exponential increase in solar power. (Gosh, I wonder why)

https://scripps.ucsd.edu/bluemoon/co2_400/co2_2k_ce.png
I'm at the tail end of two of these, of ~10 in my career. They are always tough, always a bit of chaos, and all different.

Planning is important, and avoid committing to targets or deadlines until you have your arms wrapped around what needs to be done. This can be wide-ranging, and include: product parity, contract management, internal asset development (project plans, test suites, customer training, etc.), customer change management, and team throughput.

You have few clients but large impacts. You likely want to pick the friendliest one and give them generous terms to be the "test case". Expect it will take 2x longer than your estimate.

Do as much work on parity as you can: what are the differences between v1 and v2, and how will you bridge them? If data migration is involved, you will need tooling and team training.

Inevitably you will find that customers move slower than you like and are using v1 in ways you did not expect.
It's pretty clear from the tone of his comments that he's not complaining, knows he was being unreasonable, and is treating this whole thing as a joke already.
Smalltalk can use a similar bootstrapping method, which blew my mind the first time I read and understood (see https://ftp.squeak.org/docs/OOPSLA.Squeak.html, "Smalltalk to C Translation"). In that world, images can easily obscure some of the lineage. Scheme has the advantage of having a standard to hold dialects to. I am watching this project with interest.
HN often submits articles about Forth and derivatives. Are concatenative and stack-based languages kind of the same thing? (for example, Wikipedia classifies both "Forth" and "Factor" as "concatenative (stack-based)" programming languages.
Lol, I got hit with this: "You're Temporarily Blocked: It looks like you were misusing this feature by going too fast. You’ve been temporarily blocked from using it."

Anyone using this may want to s/1000/2000/ on the first line.
They could put out a big production line of cheaper reactors, but the problem is that their navy boats are a target for missiles, which means larger risks of bad incidents. So they pick carefully

Cargo generally isnt a target in the same way
https://herrbischoff.com/2021/03/herr-bischoffs-ip-blocklist...

It’s a start.
Another awesome fact about Tanenbaum is that he was the person behind electoral-vote.com. Prior to everyone having their own model and Nate Silver (err, should I say Poblano?) running the table in 2008, this was the place to go understand the 2004 US Presidential Election between Bush and Kerry. Hugely helpful for many people to understand polling and statistics.
The picture of modular housing isn't at all what this project is going to look like. Yes, prefab does add some constraints but you only produce a building that looks like a stack of shipping containers if that's what you want.

And, is this development really so bad? There's a bunch of additional housing created; Costco gets their store built; we have mixed use, where a lot of people aren't going to need to take a car trip to do their shopping.
What are the actual steps using the UI if one chooses to do it manually?
That is an inflation adjusted number
Study Finds Self-Driving Cars Are Safer Unless They Have to Turn
You getting stranded and stuck is one thing, I guess. This could arguably happen with your own car too. But what if that USPS supervisor, or in another situation some upset business owner, makes much bigger deal out of it, things could escalate...
I like the idea. The main thing I'd want to adopt this design is a comparable ability to inject environment variable secrets into lambda that ECS offers.

It'd also be nice to have a better log aggregation strategy for lambda than scraping cloudwatch, but that feels less important.
This is a nice marketing article, and while I completely support the transition off fossil fuels and onto renewables, I don't think it's the right approach - it's better to be upfront about the challenges involved in feeding intermittent energy streams into an electricity grid where demand is not aligned closely with primary production, neither on a daily nor a seasonal basis.

The authors of this kind of thing should take a cue from the financial reporting on the 2008 economic crash and films like the Big Short - people can handle complexity, they're interested in hearing about default credit swaps and CDOs and the internal mechanisms of complex financial instruments - so they can certainly handle somewhat difficult energy concepts.

Thus, you can tell people that if you want to run 24/7 on solar inputs alone, then at peak noon you might need your solar system to be producing twice as much power as demand is drawing from the grid, so that the rest can be diverted to storage for use in the evening and morning. If you want to get through a cold wet northern hemisphere December, then you'll need even more solar to divert to chemical fuel storage of some kind for that time period.
> As I said before, I do believe that this is the future of CPUs core

It is not. Or at least not the future, singular. Many applications still favor strong single-core performance, which means in, say, a 64-core CPU, ~56 (if not more) of them will be twiddling their thumbs.

> It's in the environment that the weight of x86's legacy will catch up with us and we'll need to get rid of all the waste transistors decoding cruft.

This very same site has a well-known article named “ISA doesn’t matter”. As noted though, with many-core, having to budget decoder silicon/power might start to matter enough.
The UUID is "sent" to the server in the signed certificate. Not in the clear or over an app protocol like HTTP. There's no way to fake this UUID.
My MSc research at UWaterloo involved mapping photovoltaic viability in Canada. The data was somewhat uninteresting because the conclusion was: pretty much everywhere.
7 words: "Earn more, spend less, invest the difference."
There's no such thing as 'counterfeit parts'. There are 'parts sourced from cheaper suppliers'. I keep saying it it, but EVERY MANUFACTURER both local and foreign will source parts from wherever they are cheaper.

How else are they going to keep their shareholders happy? And they have a responsibility to do just that. Their shareholders should always come first.
There's an argument that "aggressive Boston driving" was a result of how the old Central Artery was built.
> Most people do trust them already,

Forced to trust them. Windows is the default at most companies, and the cheapest laptops on the market (the ones that will shove ads all over Edge and your start menu) run Windows also.
Terraforming or depopulation. I prefer the former.
Again, completely off the mark here. To create any CSR, bifrost or not, you need the private key that the CSR represents.

> Creating a CSR creats my private key for the CSR...

Not really sure what's going on here tbh.
Here's a list I put together:

https://usefind.ai/searches/startups-seed-to-series-c-workin...
Sure, there are lots of ways to avoid that particular risk. But the point (and the point of the article as I understand it) is that the need to do so is not necessarily an intuitive property of signature algorithms.

As the opening paragraph of the article points out, there is a lot of interesting vulnerability space surrounding reasonable properties of cryptographic algorithms that reasonable people might incorrectly assume they do or do not have. This is not necessarily a critique of any particular algorithm, but a reminder that designing secure cryptographic protocols is fiendishly difficult and that all else being equal, designers and users should probably prefer algorithms and protocols designed to limit surprising properties or catastrophic failure modes.
Gorilla glass or sapphire glass might have enabled lighter tubes at a higher price, had CRTs retained popularity, but from what I can see, Corning never even considered it as a use case for Gorilla glass in their original 1960s attempt at development.
Why would a person who objects to Facebook tracking them via their actual profile not object to Facebook tracking them via inferences?
I depends on what you view as the real history. If you link each pull request to a work item you’re not going to really need all the commits on a development branch, because the only part of the history which matters is the pull request.

I think people should just use what works for them, if that’s debase who cares? The important part is being able to commit “asd” 9 billion times. If you can’t do that it will tax your developers with needlessly having to come up with reasons why they committed before lunch… that meeting… going to the toilet and so on.
I think the solution will come from storage but also from a massive grid-wide ability to shed non-critical loads on-demand. The current grid is built on early 20th century principles, before we had real-time digital communications.

As a though experiment - imagine a 19th century world suddenly getting all of our current digital tech and wind farms and solar power - there would be no point in trying to create a "static" grid where producers and consumers weren't communicating with each other. Every consumer would negotiate power availabity based on momentary price.
OP here, I've updated the script for a bit more robust support when dealing with slow/delayed endpoint calls! Thanks for the feedback, HN!
So how about a compromise and get interlocking triangles?
Are there benefits to distributing generation? If I can top up my car on a sunny day the grid doesn’t even have to know.
How do I see how a site is handled in DNS?

For example https://www.whatsmydns.net/#A/www.bispebjerghospital.dk shows that the address is only resolvable from some locations.

I contacted the hostmaster and they admitted they have blocking in the DNS server.

Would be nice to see this also on this site.
> And, is this development really so bad?

It depends on how it's managed. If there _happens_ to be enough demand that people will accept it and pay a profitable rate, it might be just fine, but the cart is before the horse on this, so I wouldn't necessarily expect that outcome without other evidence to support it.
Wow, that's pretty neat. I've not seen modern western square dancing and this calling business before. Certainly there is a language of moves/steps here that the dancers know well.
Agree. Arm-chair generals above think otherwise.
No, I'm defending common sense. If you're going to insist they technically said 'unlimited' they're going to insist they technically didn't say 'forever', so what indeed is the problem? There's a letter and a spirit of a contract and everyone who isn't intentionally trying to be petulant understands the difference or is going to be treated in the same way.
So far. Hence, education / culture issue.
Do senior Devs actually want to work on such a thankless project?
Yeah, like what? TikTok, or some other Big Tech platform?

Have you tried to reach customers these days to promote your art?
If you need investment advice, I would recommend putting your money in an S&P 500 fund. Source - that's what Warren Buffet recommends most people should do.
About 300+ manual clicks on average :/
There are some areas of Boston where the roads are pretty bad. I took a friend into the medical area around the Fens recently and it was really a cut over here and don't let them in sort of situation.
I didn't abuse it.

How does my contract change, again?
you should try driving with openpilot and compare it with FSD to see if they're equal since you are making this comparison
You get to define plenty of warning?
I wouldn't consider the working of an electron gun to be an introductory physics context.
I don't really understand your complaint. All the issues you raise are true, but there's nothing factually incorrect in the article is there?
Day #1 of any N-month long migration/rewrite project I've participated in:

PM: "Fill out this spreadsheet with key dates leading up to the project completion."

Me: "First, that's your job, not mine. Second, I literally just got here, I haven't even drunk my coffee yet. Hi, my name is Jiggawatts. I've only just heard of this software we're migrating ten minutes ago."

PM: "Yes, yes, but the customer asked me for cost estimates and timelines."

Me: "I asked for a Lamborghini packed with supermodels, but I didn't get that either. Tough break, huh?"

PM: "It's not an unreasonable request!"

Me: "Without time machines and/or a magic crystal ball, it is. Do you have a time machine?"

Etc...

We all recognise this, and it's a symptom of an underlying problem.

Really, what ought to occur is incremental progress and demonstrable deliverables. If you go off into a cave for two years and come back with something the customer doesn't like, then you've caused a business catastrophe.

I've found that businesses and customers in general prefer incremental improvement. One trick in .NET land is to use something like YARP[1], which lets you totally rewrite the app... one web page at a time.

Another management trick on top of that is to not demo the last few steps. Complete the last few milestones of the project quietly, without reporting this up until the very end. I guarantee you that everyone in charge of the budget thinks they can "save money" by skipping the "last 10%", even though that results in 2x the ongoing complexity because it means the legacy components must still remain live and deployed to production.

I guarantee that the only way to prevent this is to lie to management. It is biologically impossible to insert these concepts into the brain of a non-technical manager, so don't even try.

[1] https://microsoft.github.io/reverse-proxy/
A small child could kill hundreds of people with a single gun (depending on the type). Firearms (including bombs) are force multipliers far beyond any bow or spear.
Sounds like the problem here is using the wrong tool for the job. Signatures are designed to prove who sent the message. If you want to hide who sent the message, you need something else. In your example, you would take an extra step of encrypting the message with your girlfriend’s public key so only she can decrypt it and then verify it came from you.
Fun! Flights, shopping, scholar, trends, tensorflow, Go, recaptcha, pixel, Chromecast, firebase, translate...

Re "too trivial to count"? We're commenting on a thread that involves an award given out for someone who wrote an excel script...

Re "not good": From whose perspective? If it makes company more profit then it's hard to say that it's a bad thing...
My experience on multiple cloud projects over many years is endless fiddling and problem solving and spaghetti.
It looks like with this, you get macros and a repl, though.
I sort of get the complaint about matching production and usage, but it seems worth pointing out that in climates that encourage air conditioning, peak solar output and peak air conditioning usage are reasonably well matched. That's not a 24/7 solution of course, but it's substantial progress all the same.
If there's a place in the world I would expect to not have capacity issue, that's Google. If I were a judge, I wouldn't rule it's unreasonable for users to assume that it can store as many data as they produce, after having committed and advertised to do so.
I can't see things in my minds eye. It's not a thing for me
Are firearms the only way for people to be defended?
What is the motivation to prefer untargeted ads over targeted ones?
> One rule I have for any rebasing is, when there may be more than one person using the branch, no more rebasing that branch.

Is it just me, or is it genuinely funny that whenever someone does this I think of Deep Thoughts by Jack Handey: “When you're going up the stairs and you take a step, kick the other leg up high behind you to keep people from following too close.”
You can get 500TB+ NAS appliances on ebay for 10k. Universities outsourcing this stuff WHILE STILL HAVING IT support staff at the same or higher levels is insane.

Run your own schtuff people! At least when you outsource your supposed core competence, then cull your infra and your staff.
It's impressive but there are multiple startups in the US working on fusion power.
Inside Netflix's bet on advanced video encoding
> Tesla: drive the price of EVs down to parity with ICE cars while delivering a superior product

Tesla was more than willing to jack up their prices and maximize profit when they could. What drove prices down on Teslas was real competition from the incumbent manufacturers. And inflation cooling people's willingness to blow a bunch of money on expensive cars. And CATL making batteries less expensive. And even then, their cars are only at parity right about now, with a $7500 tax credit. And also only if you are fairly loose about what features you need to consider 'parity' achieved.
> Make a script that makes a commit every second or every time you finish editing a line. It might be interesting later, yet that's usually not how people use git. Those changes wouldn't be meaningful units of work.

Every Jetbrains IDE does this, and VSCode has it's own equivalent feature. They don't use git, but same thing really. It's one of the most useful features ever IMO.
Not quite. Could be Call Level Interface, Command Line Interface, Common Language Infrastructure, or Clintonville Municipal Airport which has the airport code of "CLI".
There was also a brief reign of plasma TVs in-between, now almost a forgotten technology
and he is banned from Facebook.

(for some that is a relief for others it is serious)
It didn't matter in Franklin's time, but it came to matter later, due to the discovery or invention of devices in which it matters which charge carrier is moving.

For example, in naming the parts of a NPN bipolar junction transistor, the negatively connected terminal is the "emitter", and the positive one the "collector". The base-emitter diode arrow points toward the emitter.
99% sure gmail used to say Unlimited, Forever, waaaayyyyyyyy back
Buildings that could have been beautiful and enrich the city and the lives of tenants will end up being stack of containers to bypass government imposed minimum wage and endless regulations.

No wonder why soviet union buildings looked like a bland block of concrete.

If this is not a cautionary tale on the dangers of regulation, I don't know what is.

Congrats to Costco for finding a trick and getting things done, despite the government.
One of the times aphantasia has been brought up here somebody posted a guide to training your brain to see more vivid imagery from someone who alleges they started out aphantasic and trained themselves to not be.

Does anybody have the link, I've been searching for it for like a year since I forgot to backup my bookmarks before a resinstall.
No. I go to the grocery store. Where an army of robots controlled by farmers has already done it for me. We're so good at this more than 1/3 of it goes to waste. We export so much food it literally disrupts world markets.

The question you want to ask is there ever a point where population's psychical space demands overcome the space required to feed those people? We are nowhere near this limit.
Reminds me of the ill-fated Larabee, which was supposed to be something like 50 Pentium-like cores in a GPU-shaped trenchcoat.
so interesting. I've somehow always supposed that it was ms-dos that decided to be different.
Primordial black holes should be far smaller. Super-massive black holes were thought to form through accumulation of matter ("feeding") only. This super-massive black hole is present in the early universe (given how far away it is), and exists much earlier than current theory predicted.
They made a 40" CRT. I used to find them for free all the time on Craigslist because people just wanted them gone.

Here's a pic of one:

https://i.ebayimg.com/images/g/VkcAAOSw1jpij-aq/s-l1600.webp

I found a brand new one from someone's house where the person had died a long time ago and three of us lugged it back to my house (three people can barely lift it). I grabbed it for light gun games, but it uses some sort of digital filtering on all the inputs which stops gun games from detecting the scan. I was going to take it apart and figure out how to bypass it, but I lost it in my divorce lol.