skysight-inc/HackerNews huggingface dataset:
> I don't know whether we'd argue this DC->AC is harder/easier than an ATX supply (AC->DC) (probably not?) but this was quite an impressive competition, almost a decade ago, that resulted in probably some of the most power-dense, highest-efficiency power conversions that humanity has ever gotten up to.

The LBC was misshapen because they had an odd requirement: Be single-phase. A three-phase inverter (or rectifier) naturally has low DC ripple and is both more compact and more efficient than a single-phase inverter at all power levels. All of the winning solutions had extra energy storage elements which added inefficiency and bulk which a three-phase inverter would not have needed.

With that in mind, the LBC was a little silly. A three-phase machine at the same power level would have been much smaller than any of the "winning" designs.

A high-efficiency ATX power supply has additional requirements that the LBC didn't need to meet: Isolation. This implies the use of a transformer to protect the low-voltage DC side from the AC side. They typically accomplish this by rectifing AC, using a transformer-isolated unidirectionally optimized DC/DC supply to 12V, and then provide a handful of lower-power DC/DC converters to derive the other voltage levels used by ATX. A modern unisolated DC->AC machine is effectively symmetric in its power flow, and also functions as an AC->DC machine.
>Not to be an ass, but playing with css and html isn't programming. At all. It's making web pages.

... except you can literally make desktop and mobile applications now by "playing with css and html"! ^electron -- shudder!^

Part of the reason for the JS mess (which people have been bitching about for years and years) is how easy it is to dip your toes into. Match that with how easy it is to create a "gui" now with HTML and CSS, stir in an endless bunch of half-baked support libraries built by people that just learned JS last month and you get the perpetual hell of the JS ecosystem.

And now that it has been adopted by startups and traditional companies, it is here to stay for a while.

Half of my development time when dealing with a new JS project is un-fucking some JS dependency that I never wanted that lives deep in the bowels of npm_modules.
Generally, I recommend Reaper reaper.fm for any audio related tasks. I've used it for personal and professional projects for years now. If you can be more specific about what doesn't seem to be "that good" about the software you've been testing maybe I can give some more targeted recommendations.
The bigger question is if it will be more successful than the partly accidental geoengineering that has been taking place over the last couple of centuries, or if it will be a speedup button.
out of that list, rust doesn't offer "no macros and no metaprogramming" and "no hidden control flow". maybe these just aren't things you care about?
My thoughts exactly... I'm not sure if you can call it a reddit for podcasts if there's no logged out view
Bear in mind too in winter the days are shorter, sunlight is weaker, and you're using *aaaaaaall* of the electrical goodies.

Even down south here at 56°N there's about five hours of sunlight in winter and as you get further north it just gets shorter. That's about enough charge to get the length of a supermarket car park.
> There is room for using one indicator over another for any given application.

Absolutely, but this kind of debate needs to be done in good faith and with the understanding that whatever new basket of goods one comes up with is unlikely to be applicable to any more people in the economy.

The basket of goods is like a a medium shirt. It's not going to fit anyone very well, and it won't fit most people at all. Swapping the shirt out for a large isn't going to improve the fit for people as a whole, it will just change the people who fit in it.

The curse of dimensionality rears its head when talking about "averages" over a number of dimensions. There's not really a good methodology to distill such a complex topic down to a single figure.
Fairly certain that ability has been around a few years.

I left that comment there for folks who didn't know that was possible, as going the SNS -> SQS -> Lambda route is what is most popular and most written about.
And pretty much like every over-reaching policy, it will be circumvented by the bad actors and be used to oppress law-abiding people and to keep the status quo.

Still, crypto could be used for the payment and KYC be done through other means.
You're welcome to design systems however you want. But this is, put simply, bad advice; and when sharing advice like this to people who may be learning these things for the first time it's critical to communicate not just what these complex components are capable of, but how to best work with them to build reliable and effective systems.

If you have multiple heterogenous consumers, do not use a single SQS queue.

I can't even comprehend how you would engineer around the issue of consumer re-processing. You can quote metaphors all day; if you love the idea of dumb pipes, why doesn't the city transport clean and gray water in the same pipe? Do you want to wash your hands using flushed toilet water?

Similarly, you can't engineer around heterogenous consumers grabbing a message, putting it back in the queue, then consuming it again. You can make them smart! You can have them say "woah hold on, I already saw that message I don't need to see it again put it back". Or, you can make them idempotent so reprocessing isn't undesirable. But its still reprocessing; its still a huge waste, and will probably require external state to manage. Moreover, there's literally no system guarantee that Consumer2 will ever see that message; it'll probably see it, fifty-fifty, well then again if one consumer is faster at accessing the AWS API than the second, who knows, anything could happen, but at least its convenient?

The city doesn't require every household to have gray water filtration. Because that would be insane. The pipes don't have to be "smart". We just build two pipes!
Optimizing for efficiency isn't a bad thing. The real problem is the larger economic feedback loop based around keeping the number of hours worked the same. So the efficiency gains are effectively lost, and the average worker is left still depending on the ever-optimized structure rather than being able to accumulate enough wealth to escape it and create new structures.
Won't the population issue take care of itself at some point and peak? We already see stagnant or decreasing populations in developed countries.
A financial system built on top of transparent and trustless components is opt-in. That means that if all my currency is based on trustless structure I can be responsible for my currency and when it's transparent I can be more aware of how the fungible units of my currency are being used in the wider ecosystem.

As it stands, private banks (the fed) have not only the ability to manipulate my currency, they are actively encouraged to do so.

Sure you can build scams and call it cryptocurrency in similar ways you can scam people in fiat. I'm certainly not claiming crypto solves all problems, only that it provides a solid foundation for society to build a better financial structure on top. That improved foundation does not mean society will build stronger on top of it, it just means that it gives us the ability to do so if we choose to do so.

I don't believe it's possible to have equality in our money without rules that apply to everyone. Crypto can apply rules to everyone, equally. Compared to our financial institutions today that are very much tier privilege controlled by the government, which appears to have strong malicious influence from the largest stake-holders in our current financial institutions.

I don't believe it's mere coincidence that wealth distribution is becoming dangerously unequal, I believe that is a direct consequence of our financial system.
As long as the spice must flow whatever is necessary to keep the spice flowing will be done. For he who controls the spice controls the thing that is not the spice.
It's hard to connect interest rates to house prices historically, but I think that's because there's two scenarios going on, with some substitutability, but a general move to the latter over the last 50-30 years due to zoning and planning changes and urbanization.

In areas where developable land is very plentiful - rural, deserts, minimal environmental/nimby protections, etc. - land prices will remain low and house prices should be constrained by building costs. In the same way that we don't expect TV or car prices to go up very much with lower interest rates, even though you consume durable goods over 20years, as competition holds the prices to what it costs to make rather than how you benefit from them. Over the long term, it used to be that house prices tracked construction costs pretty well.

However in areas where the fixed quantity of land is binding - urban, or areas with stringent protections and managed growth policies - land and house prices will be bid up to what people can afford via monthly payments, and will therefore respond greatly to interest rates (and IR expectations)

Further add on that high property taxes in some regions can dilute the costs associated with financing changes (if interest rates increase from 1 to 2%, but you're paying 5% in property taxes, that's only a 7/6% increase in your costs)

edit: to summarize, where supply is elastic, interest rate reductions should cause quantity supplied to increase, price to remain the same, and monthly costs to decrease. Where supply is inelastic, the quantity stays the same, monthly payments stay the same, price increase. We've possibly moved into an environment with more supply inelasticity in recent history.
The examples in the article are all realistic, but I'd like to add something important: This is using the NPM ecosystem and JS dependencies.

A language's tooling and ecosystem are arguably part of the language itself for practical purposes. So, the article is a fair assessment. I'm making this distinction because you can use JS in what it accels at without invoking build tools and dependencies: As an imperative language making DOM manipulations without the IO-induced latency of querying a server and waiting for a response, JS gets the job done.
> Best I could tell, neither of them looked, at least not more than a minute.

I once interviewed a guy with a nice, short 1-pager résumé—not from lack of experience, just a solid, terse document. Not just out of school. Had three or four tech jobs in his history.

He listed one research paper near the bottom, that he'd co-authored in grad school.

I found the paper, skimmed it, and asked him about it in the interview (a lot of times in interviews I just ask candidates about stuff that it seems like they'd know about, that I don't know about, to satisfy my curiosity—I have no idea whether this is good or bad interviewing technique, but my intuition is having someone teach you about something you don't know, that they do, is probably at least as good as asking them to tell you stuff you already know) and he told me I was the only interviewer who'd ever brought it up at all.
It isn't ignorance - the people who complain the loudest about the JS ecosystem are the people who use it the most.
Conversely, I find Tilt Five to be nowhere near as interesting to me as Dynamic Land. Tilt Five doesn't push the envelope on computing further as far as I can see, but rather is just an expensive game peripheral for windows and android phones; Dynamic land is attempting to develop and enable new forms of media, especially communal media. The two projects shouldn't be held in the same breath IMO.

Besides, the Tilt Five developer program YouTube commercial[1] is the worst. It's like an xbox 360 reveal video at CES or a Qualcomm presentation about digital natives.

[1]: https://www.youtube.com/watch?v=a-7lHqyBQeg
not for the merchant.
People in this thread have extremely optimistic expectations of the police. In this country at least, the police don't protect poor people, kids or no. It's not what they're spending their time doing.
If you could name even one I would remove the "dogma". I cannot think of why anyone would want to do that. And if someone did want to do that they would have to have a very compelling reason to complicate what is usually an easy thing (One action listening on a queue)
I'm not sure I'm following. You can jump into any podcast discussion via the homepage, either by clicking a comment or by searching for a podcast. You don't need an account to see discussion boards and you can even comment anonymously.
They can potentially allow you to delegate key generation to a third-party hardwire device, i.e. Yubikey or a Smart Card, but then you're trusting the vendor of that. It's pretty hard not to have to trust somebody. They can at least protect against individual rogue employees with reasonable change management processes that involve simple measures like separation of duties and mandatory vacation.

If you're trying to protect against compelled change management by law enforcement, unfortunately, your only option is illegal providers, which are likely to be inherently less trustworthy.

I really question who you think this is misleading. Normal users are not trying to conduct illegal activities in private, and leaders of drug cartels and what not are well aware that they need to do more than use paid, E2EE public services for their IT infrastructure needs. Even the other popular targets of nation states, militaries and intelligence services, use their own private infrastructure for that reason. A regular person can't feasibly do that, but if you're the Cali Cartel or Al Qaeda, maybe you can. I have trouble believing that Swiss law enforcement coming with a warrant is "one of the most important sorts of attacks" for any significant number of Proton users. If it is, clearly don't use them, but you also need to go a lot further than that, probably being a credible threat to murder anyone you do business with that seems likely to sell out, moreso than law enforcement.
Weird example, do people actually use multiple consumers doing different things to a single message? You just queue multiple messages with different properties and consumers process things the same way.
I agree there were many others (beyond even these I can think of a several), but I think Ryan was mainly referring to was how many were regular online CTFs at the time.

Wasn't both barcode-shmarcode and oCTF both more in-person events than available online?
Show HN: A minimal approach to automatic, manual and persistent dark mode
I love stadia but it’s been on my mind that it may be dead for a while now. I guess I’d just buy a pixel with the refund they give me if it’s Google credit
This seems an awful lot like you demanding users have a particular skill you want them to have for $reasons. This is silly, use orings.
I think one way this can be more acceptable is to redirect the camera to view the hands above the keyboard instead of having to wave my hands in front of my face. Interesting to be able to enable gestures to swipe desktops without using the trackpad.
Climate geoengineering will be rogue. Just like there isn’t consensus amongst countries on dealing with climate change, there won’t be consensus on whether to geoengineer a solution. Eventually climate change will get bad enough, with whatever crop failure or burning heat wave, a country in dire straights will just attempt it anyway as a last resort for themselves, regardless of the decrying from other nations. The result will be anyones guess.
The fact that Musk doesn't promote or even allow non-Tesla owners to charge electric vehicles at Supercharging stations demonstrates his tendency for monopolization, at the expense of mass electric vehicle adoption rates. Musk would sooner see his employees living and dying on Mars than fix carbon emissions on Earth.
The article claims the writers are Indian.
HTML & CSS in Python is ugly. Is there a way to split those from python ?
I wish I knew, but I'm unsure. I think with effectiveness in mind, the Effective Altruists are your best community to explore and interact with. There are various Facebook groups (and other areas on the web) within EA that focus on specific topics (environment, well-being, etc) so I suspect you could find something if you search around and ask around.

https://www.effectivealtruism.org/

ps - A humble thought. As tempting as it is to help within one's community, it's worthwhile to recognize that given the inequality in the world, and that it's just a luck-accident that you were born in this community rather than another, and that it very likely is the case that you can do a lot more good by focusing on individuals living in less-well-off-areas than what is nearby, it is good to reflect and see if you'd be willing to direct some of your philanthropic actions towards the more-effective endeavors.
Whether it's OK for a company to co-opt an English word for its name depends on how much confusion and inelegance it causes. I didn't have a problem with their original name.

That said, "facebook" was not in my vocabulary as a native American English speaker, and I'd wager that was true for over 99% of Americans. My impression is that it's something that only existed at Ivy League schools. Perhaps regular colleges also had them? Maybe someone could fill me in on that.
i read for about an hour every morning. reddit, hacker news, newsletters. Gives you great exposure to everything that's out there and what's changing. I highly recommend just picking simple function you need to write and work on that in the mornings. work on building isolated, modular code. I tend to write more functional / interface bases code than OO these days. Easier to reason about and maintain.
That’s a good idea. Basically having a blog saying what 5/3/1 is. It’s a narrow line to walk on as I didn’t write the book and want to respect the author, but I think that I could probably do something like that.
Not that I agree with the GP, but I think it’s easy to conflate “node”_modules with “modules from NPM”. Bower was once the recommended package manager for front-end assets, but NPM overtook it. I use Node daily, but 90% of my packages are front end.
That is crazy I once suggested an idea similar to Stratospheric aerosol injection to slow down global warming, by using nukes to throw large amounts of dust into the air and everyone downvoted me to hell telling me it wouldn't work, glad to see the idea wasn't as crazy as I thought.
COVID stay-at-home has revealed that micromanagement and all the customary social signaling isn't necessary, more like it.
Yes, we're being paid for another month or 2 to get trained. I'm planning on staying until the end of the training, but the thought of having to go through the job seeking rigamarole is weighing heavy on me personally.

Do you know if there are places that are hiring junior people with these sort of certs?
Can I ask why you need permission or care about assigning a nationality in the first place?

Also, the opposite of your country is not America. Aka just because you don't observe something in your country doesn't make it automatically American.
> Imposing the side-effects of geoengineering . . . on unwilling countries is bound to have geopolitical ramification

I would think that the arms industry would get behind that. Thus both of their political parties here in the US would vote to fund it - freedom! As long as there's profit for those companies there will be "political will."
Totally, but startups (literally?) do not have that option.
Since I guess we're talking about Earth, where's the "No, because it's a bad idea" option?

Go prove you can make Venus or Mars livable before you poison the ocean or skies and unintentionally kill off all the fish or send our only planet into an ice age.
Sometimes there are higher principles than free software.
> It's literally the name itself "node"_modules, it's designed to be used with node.

That’s the problem. It’s not JavaScript. It’s not any part of the ECMA standard, it doesn’t work in runtimes other than node (read: the browser) yet it lives in the .js files making them not truly JavaScript. You have split the language.

The syntax isn’t part of the language and was designed in such a way that it cannot be polyfilled. This lead to a thousand packagers that would not be necessary at all if a sane syntax had been chosen. The creator of node himself has said making node incompatible with the browser was one of his biggest mistakes.

https://medium.com/@imior/10-things-i-regret-about-node-js-r...

> There are also countless boilerplate project with webpack setup already so you can get reference from there.

That’s literally the other problem! People just copying boilerplate without understanding it. That’s not a proper solution. That’s not a maintainable project, that’s copying other peoples homework and getting yourself in over your head.
This is exactly what I’m after right now. My server at home runs off 2 big docker compose files and I’m looking at other options.
While I would not object to what you propose, I doubt it would change behavior significantly. People who are inclined to think about the interest and overall costs are already easily able to access that information. People who aren't inclined will see 3 additional pages among the 120 pages they see during closing or 30 they see during mortgage application/qualification process.

People who can't (or don't want to) math aren't likely to suddenly do so because of an additional disclosure.
It's not enough to notice that something's possible. You have to do it for a good laugh and show your friends. Sorry, Valve.
Instead of trying to stop it, have it send fake data (photos, geotags, etc.), and direct Russian forces into kill zones or capture.
That's a different problem also solvable with Vitess. For those smaller tables, you can define them as a reference table, then have the same rows on every shard, so you can continue to have FKs to all of those.

https://vitess.io/docs/13.0/user-guides/vschema-guide/advanc...

When you're choosing your sharding keys, you want to design it where the bulk of your operations happen on a single shard, often a tenant/customer id. That guarantees that all customer data lands on a single shard, with FKs across every table you want.

We're running on ~40 shards across 6 keyspaces, and there are very few cases where we can't use FKs.
All of this is already done in Lisp. Greenspun's 10th rule.
I think C and C++ are a fair comparison in that their build ecosystems also a bit of a mess. I offer 3 counter-examples: Rust, Python, and JS-without-NPM.

edit: After reflection, I think Python straddles a middle ground. If you use modern packages and Python 3, it can be a smooth experience. If you use older (improperly-specified) packages, or FFI-wrapped-libs, it can turn into a mess too.
“We’ve always subjugated and mistreated the working class” is not the win that you think it is.
> In fact, crypto is completely dystopian because there is absolutely no space for cash in it, and further, by being distributed and therefore pseudonymous at best, it actually opens massive privacy and security pandora boxes.

Is this true of all coins though? I know little about crypto, but I gather from reading on here while the privacy of bitcoin was greatly exaggerated/false other coins use actually privacy respecting schemes. Of course, that would assume that the schemes they use work perfectly which is probably a ridiculous assumption.
> several things are out of equilibrium right now due to supply chain disruptions and a demand surge after the pandemic.

And some things (most of them actually) are never at their equilibrium price for many reasons (but mostly because the characteristic time to reach equilibrium is higher than the frequency of perturbations). A bit like how it's completely fine to still have snow outside even if the temperature is firmly above zero Celsius.
What is the format for article writing?
One participating airline that is a tiny regional carrier in Alaska.

Yeah it exists alright.