skysight-inc/HackerNews huggingface dataset:
"made from plants" will need a citation.

The Porsche/Exxon syn fuel uses natural gas as it's feedstock, for instance.

I'm pretty sure the Mazda pr guy was just smart enough to omit that detail, not that they are hiding it's magical eco friendly origins.
If possible, I would prefer deriving the "userType" from UserAttributes.

I see various methods for doing so are covered in the follow-up post linked at the top of tfa.

This is also avoidable if you have proper class/interface hierarchies, where the type "field/key" is the type itself.

In the case it's not possible and there really is only 1 type that is fully applicable to both admins and normal users then I would probably be fine with either approach (although I'd consider updating the return type to get type safety between admin and normal users!)
Some scattered thoughts:

Just today, I built a complex order editing form in vanilla Javascript with AJAX. It's over 900 lines of Javascript where half of the code is state management boilerplate, painstakingly ensuring the correct effects are run when the user changes an order line's quantity or picks another product. We currently can't use libraries with our stack, so it was necessary to write it like this, but it made me yearn for the frameworks.

The frontend landscape isn't more complex than it needs to be, it's as complex as we need it to be. We take many things for granted in our modern stack. Sure, Javascript has come very far in many areas, but it also lacks many things that are regularly needed and the tooling covers for that. Things like state management, functional composition of layout and form validation are things that Javascript simply doesn't (and probably shouldn't) provide, and that's why we have libraries/frameworks for those.

I see many people bashing on Redux in the comments section. Redux can be overkill if you're writing a single-page (like, actually one page) website, but as soon as you need to manage user credentials and state that needs to be persisted across many pages (think shopping cart), Redux becomes indispensable for me. Sure, you can use something like useReducer, but it doesn't really compare once you add redux-toolkit to the equation.

I agree with the general sentiment about the npm ecosystem. Like with anything else, taking "don't reinvent the wheel" to the extreme causes chaos because the entire world is not a monorepo and we have to rely not breaking one another (which fails often). My rule of thumb for whether I should reach for an npm package is "can I write this correctly and with tests in an afternoon?". Things like arbitrary-precision decimals fail that test, but many others simply go into utils.js.

To summarize my thoughts and make myself a bit more coherent: The frontend tooling is as complex as we need it to be. Evaluate what you need and build your stack with that. Don't join any cargo cults, both for and against framework use.
Oh, you mean some non-zero investment is required? What change doesn't require investment?

In all likelihood, gasoline transportation costs an order of magnitude more than electricity. And that's not just infrastructure that is already paid for. There is a much larger maintenance cost, an ongoing labor cost, and a much shorter useful life for anything related to fossil fuels.
> I'd be interested in why you had to go through alot of effort to cash your check.

I’m not the commenter you are asking from I also used to live in central europe. There as far as I can tell the concept of a “check” simply doesn’t exist. So much so that I don’t even know what is the equivalent word in the local language. If I would get one I would need to go to my bank in person and ask them if they can do anything with. I would already count that as a hassle, but I just looked it up online and it seems my bank doesn’t handle checks. There are rummours online that some other banks do cash checks, but it seems some of those have changed their policy since and they are no longer accepting checks either.

All in all it works as well as being paid with a rai stone or a cowry sea shell, while lacking the aesthetic benefits of those.
who said anything about multiple choice?
I guess the same way as when using the Latin script (which is the script you and I are writing in).
I dunno. Lots of users seem to wake up and say “Gimme a UI with rich interactions, super low latency, offline support, and real-time sync.” Even for B2B “back-of-office” software, the standards for software usability are really high, especially for new entrants.

Those kinda features are hard without a pretty complex frontend.

Not saying those things are always necessary, or that people don’t add bells and whistles where they aren’t wanted.
I don't remember ever having a mental breakdown. I am rarely "happy" but I am 100% satisfied with my life.
And with the loose ABI model, how much more often they'd have to do that?
A host of reasons but it's my opinion that the calculus of what you can develop for what resources simply workout, and that math trumps the regrettable bloat that a portion of the population notices.

You can look at the complicated tooling of '23, the increasingly niche roles ("React state management expert"), the bundle sizes, the expanse of the browser spec and wonder how this trend is sustained, but there's a flip side to all of this: it's easier today than ever to develop well-utilized, sophisticated software with a team. That last part is important- since teams build most of the well-trafficked web applications out there it will be the limiting factor in economic equations. And all this specialization and bloat is conducive to concurrency (see Conway's law [0]).

I'm reminded of an Economist article I read that asserted that better engineering often doesn't solve a traffic problem since the pain of traffic will approach the threshold of what people will tolerate. People who don't drive because of traffic start driving until the commute is nearly the exact same.

[0] https://en.wikipedia.org/wiki/Conway%27s_law
The artifact we often use is “zoom recording of the meeting.” Which is less than useful.

For non-sensitive meetings, we record to otter and then edit the transcript using highlights, marking to dos, etc. We’ve got an otter folder structure that mimics our other folder structures. We most commonly do this for document review meetings (I work for an NGO. We write a lot of grants.) This takes time but it creates good notes, allows everyone to be a participant in the meeting.

We have other meetings — like weekly target review meetings — that use Asana as the basis for capturing notes. This works well for things that are really tactical.
You get this by default for any object with non-public fields.
I'm more than thrilled.

Glad that this crypto scam and meme stock hype is finally dying out completely.

We need tighter regulations (or new regulations) on the whole thing so that it all crashes down and crypto burns until everyone is sick of it.

Once Tether gets exposed we will see the back of crypto.
I know what I'm doing and generally like Gnome.
Anyone aware of an open source token-based system that allows users to pool hardware assets, but allow some sort of priority and fairness enforcement to reduce network abuse?
The commonly cited pitfalls are either strawmen or exceedingly rare. ASI is predictable and reliable. Not once in 5 years of semicolon-less development did it come to bite me or anybody else in a notable manner.

By all means use them in your work, but don’t treat it as ultimate truth. It is not.
The only difference from the check fraud is this: since the fraudsters — having the password and OTP — are indistinguishable from you, the bank may not return your money (out of his pocket). And since the money was already cashed out, there's nowhere to get it back from. Bottom line, you will eat the damage.
Complexity is one end of the spectrum. Browser APIs for various stuff like animation, video, audio, webgl, etc is not that easy for developers to consume. Often most of these features have their own set of sub-complexities and concepts. For e.g. drawing/animation on the canvas is relatively simple, than doing stuff with 3d animation; the latter involves lighting, viewer perspectives, etc.

And developers don't need all of these browser features every time; much less for the same project. But from a framework POV those features need to be there. Because, as a framework developer you cater to a relatively wide developer profiles.

So far we've talked about browser APIs and how a framework seems to lend support to them. Building web apps are a whole different affair. When concepts such as optimization, and, page-load speed kick in you'd definitely think of tools that abstract away the common chore of such optimizations. Again these optimizations have their own set of options, and, hence complexity.

So today the whole affair may seem complex. But really its not artificial. There was a need and hence a solution. To anyone relatively new to web development all this might seem complex. And at some level, even we humans also unjustly decide we need to have some features because "others are also doing it". This also increases complexity in maintaining those solutions.

Bottom line is, it is a relative illusion, and, it just echoes the state of modern browsers, and, modern web development trying to be vogue.
You can easily protect your hardware from all but the most determined adversaries with extensive physical access. Epoxy in ports, case intrusion detection and locked down boot chain. Use TPM2-totp for verified boot.

Your colo provider can be thoroughly owned, your adversaries can have physical access to the server for extended periods of time and still not be able to do anything because you've denied them access to any ports that'd allow DMA.

Lots of cheap DIY options for fancy case intrusion detection going way beyond that offered by mfgs. USB camera and some tape?
And as here, syn fuels are useful for satisfying regulators.
Germany's challenges for 2023: Energy, unity and China
> there are people working on rockets and talking about Mars…it’s 100% vaporware

Methane engines and atmosphere-agnostic propulsive recovery are far from vapourware. It’s not a launch schedule. But that’s a straw man requirement for “working on” something.
Actually with the way bank regulations around check fraud works, timely knowing (/reporting) that your physical checks have gone missing is important, so you do not want to hide them out of the way. Despite being just pieces of paper, there are different regulations depending on if a fraudulent check was created from one of your bona fide checks, or whether it was forged from whole cloth.
A public AP / prep school in San Francisco.

https://archive.ph/Cg8TP
There are a lot of great answers here, I'll just point out one thing that I think is important.

It feels like a lot of the complexity around frontend development comes from managing and maintaining state, particularly between different components. State management is easy when you just have a single JS script embedded in HTML. But when you decide you want a structure that is more class-like where you can reuse components, it's suddenly incredibly difficult to share state between components and ensure changes (no matter the source) are propagated reliably and are also properly reflected in the DOM. You have this whole other layer in HTML that is awkwardly and haphazardly bound to the JS side which just makes things so much more complicated to the point where React makes its own DOM instead.
Because browsers don't support server-side declarative views natively yet. FE development wouldn't even be a thing if web servers could respond with something like

<script>
const [count, setCount] = useState(0);
</script>

<template id="counter">
<div>
<p>You clicked {count} times</p>
<button onClick={() => setCount(count + 1)}>
Click me
</button>
</div>
</template>

<counter></counter>
Moderation in everything. Eat healthy, sleep, and exercise. Seek nature, and cultivate healthy relationships with friends and family.
Five human technologies inspired by nature – from velcro to racing cars
At first, only devils used JavaScript. Then jQuery/AJAX/Web2.0 made it permissible for it to be used for good. Then Apple killed Flash. Clients and employers still demanded fancy web sites that weren't just hypertext and images. Browsers still only supported JavaScript. Node and npm enabled front-end devs to build and share. All the tiny problems that front-end devs used to deal with, like minor browser incompatibilities, were papered over with layers and layers of abstractions until they naturally ended up with frameworks like React/Vue/Angular. Then the cart came before the horse, and there has only been incremental progress since then because JavaScript is still JavaScript, and the ecosystem is too big to escape.

Anyone who tries to avoid the complexity of the existing front-end tooling soon finds themselves reinventing many many wheels.
> This means that we are discovering oil faster than we are burning it.

Nope. All this means is that oil is getting more expensive.
Being More Intentional in 2023
there are many here: https://github.com/aardappel/treesheets/tree/master/TS/examp...
US ignored own scientists' warning in backing Atlantic wind farm
The credit/debit card must be signed by owner.

In my history of using debit cards for most, and now for near everything not a single time anyone bothered to check. Even back when the magnetic stripe was used.

I also was using out of date identity document for good 6 months and datacenter staff also haven't bothered to check that.
It was very clear from the start, especially seeing his past with how aggressively he litigated even minor criticisms of the tesla as if it was slander.

* edit: I forget down voting is a thing. Why I thought i was clear from the start: If someone actually cared about their private jet privacy they would be renting jets... Cause its common knowledge that one can be tracked publicly with ownership information. Or he could push for a change in gov policies, he certainly doesn't mind sharing his political opinion now.
That's an interesting point. Do you know a good reference comparing laptop vs desktop cpu performance? I'm always confused by comparisons that inevitablty are affected by other laptop specific components (differences in mgpu / motherboard chipsets etc).
Not only do I believe that a person's home is an investment, for many it is their biggest and most important investment (if not, in many cases, their only one).

When the kids leave the nest and it comes time to retire, downsizing is the way a home owner will "cash in" on that investment (or, as you suggest, moving to a less expensive community/city/state).

I'm sure you know all this but I am confused as to why you say it is not an investment. It is illiquid, to be sure, but it does not depreciate in the way that a car, for example, does. It seems to me no less of an investment than precious metals or stocks (but for the illiquid aspect I mentioned).
Well, yes. If tomorrow everyone replaces their ICE cars with EVs, then the grid won’t be able to handle that. Completely different situation, though.
Sounds like "one politician who refuses to prove the person actually exists."

https://vancouver.citynews.ca/2022/02/23/chilliwack-mark-str...
> After all, if it was entirely fraud and then what did he have to gain from killing the High Speed Rail? I guess a small fraction of the taxes he pays not going to something he didn’t like?

He’s a car salesman. He wants you to commute in a Tesla and opposes remote work.
I never understood this obsession with founding. As anyone in the technology sector knows, brilliant ideas are a dime a dozen. Execution is what matters. So what was the brilliant idea of Tesla, and what was the execution? The three people who "founded" Tesla wanted to make a tiny number of hand built sports cars for wealthy elites, and their outcome was the Roadster, a certifiable lemon. Elon's Tesla wanted to mass-produce electric cars for a mainstream audience, and the company succeeded far beyond the predictions of anyone in the legacy auto sector.
You say this, but plenty of people post short `Status` type posts on their blog just fine. See https://aaronparecki.com/notes for an example. Combination of on-site stuff, mirrors of Twitter and Mastodon content. He's one of many folks posting both short-form statuses and long-form content. It works.

If the EU has its way then interoperability with ActivityPub will make migrating followers/following easy, as it is with redirecting Mastodon accounts. Tumblr is adding ActivityPub support. Flickr is mulling it.
Because many devs now specialize only in frontend and many succumbed into new ideologies of what is right - like using React and Webpack instead of seeking simplicity in design.
when you feel {emotion} immediately say {your_name} is feeling {emotion}

go through the reasons in you head why. over time you will understand what drives it.

this may help you react the way you want vs. the way you have historically

{emotion} —> anger, anxiety, anything else deemed negative
> you just file a police report for fraud and bank will claw back funds and reinstate you

If the fraudster has your password and OTP, and if the money's gone, bank will do nothing — as opposed to the check fraud. That's why TLA is a good check fraud story.
> A general teenager or thief wanting to cause issues would not know what to do with an SDR and laptop, versus something like the Flipper making it point and click.

This is where the story falls apart. I own both a HackRF One and a Flipper. I thought it would be a great teaching tool for my kids to show them physical world insecurities. While it's a great device it's nowhere near as potent as the HackRF as a real tool. And straight out of the box the Flipper does very little from a nefarious point of view.

The "influencers" did a great job of hyping it up on YouTube and Twitter. And my guess is that the majority of the devices sold will be used to pop Tesla charge port doors for giggles. I've gone through a few different firmware and repos and you've got to have just as much interest to learn and use compared with an SDR. And in fact in many cases the Flipper is harder to use because it's limited by its physical footprint.

It's a fun little tool but it's not making much "point and click" besides a handful of known replay attacks that shouldn't have existed in the first place. If anything I hope the Flipper pushes the likes of physical access systems manufacturers / integrators to be questioned on why their systems fail to authorize access correctly against trivial attacks. This is not the fault of tools like Flipper.
It's not just looks, there are real features missing from the new control panel activities too, and I don't look forward to the day the old ones are removed. For example, to disable a network adapter, you have to go into the Vista/7 version of Network settings so you can right click it and get the context menu. It's a mess!
> We keep adding tech and tools and experiences - if you asked users - aren't improving all that much.

Nowadays, when a provider adds an "experience" resulting only in no improvement, I feel actually quite happy. The general rule seems to be (not so slowly) migrating to activelly deteriorate functionality.

Past week my bank changed their UI to show a cute animation of a hand shaking some cash in a transaction confirmation screen. And, in the process, they've removed the button to immediatelly logout after the transfer is completed -- something I used to do frequently.

It's infuriating.
But... This is FE development, you think the backend devs would like to be writing this?

Back when we all did MVC we had FE and BE devs anyways.
Thoughts after reading the comments so far:

I acknowledge ChatGPT grade models are very expensive to operate and that there are still real performance limitations/issues that make it not yet appropriate for autonomous handling of hard transactions. Yet, we still have a new level of capability that is seriously better than anything we've had before.

I'm thinking about the acrobatics I've gone through recently trying to get certain answers from airlines, mail carriers and insurance companies just to even locate the right portion of the site or the right person to speak with. It truly seems ChatGPT would have well outperformed the www and phone channels I went through as an entry point for my journey.

So, given the new capabilities we're seeing with large language models:

1. Will WELL FUNDED companies START ASSESSING chat interfaces as a primary customer entry point - not to autonomously handle hard transactions, but to at least start the customer journey down an efficient path?

2. If so, how will this play out in terms of the evolving supply chain?

And, I would add:

3. If the answer to the first question is "no", what are the key improvements we need to see before that does happen and over what timeline should we expect to see those improvements?
Vipassana meditation. It's pretty great.
Excercise, eat properly and sleep.
You won't find a better answer, no matter how you differentiate your question.
>In all likelihood, gasoline transportation costs an order of magnitude more than electricity.

This statement just doesn't pass even the most lax economic sanity check.

Why don't all the use cases where people don't care about anything other than the bottom dollar and don't run up against the weaknesses of modern batteries already run electric vehicles. I'm thinking like low daily mileage fleet of small vehicles in a warm climate somewhere with high fuel costs. Like why doesn't an EV Fiat Promaster exist and why doesn't every tradesman in Sicily run one? If the numbers penciled out then surely we'd have it, at least in some niche somewhere. We are starting to see mass EV adoption but it's right on the margin and the details on any specific use case make it cheaper or maybe not.
> const createUser = (

> attributes: UserAttributes,

> onCreate: (user: User) => void

> ): User => {

> user = User.create(attributes);

> onCreate(user);

This stood out to me, in an otherwise tame article, as probably the most terrible overthought interface possible. A literal callback function passed as a function reference to something that does three lines of code? Good luck with that, I much prefer even a slightly procedual implementation.
> I keep assuming they must have some massive upside I'm not seeing

My default assumption would not be that there's an upside in this for them, but that they're a disfunctional organization. The people procuring your services and authorizing the expense are not in contact with or unable to influence the people planning and authorizing the payment. They might not even share a superior all the way up to the board, with the procurement people reporting to the COO and the payment people to the CFO. If it's easier to spend the company's money than to save it, people will spend it. Corporate seldom rewards saving money anyway.
> It is not my job to know how the bank got hacked.

And without any explanations, it's not your bank's job to return your money.
'The tip of the iceberg': Three Picasso artworks discovered in three months
People nowadays will use 100 GB in VRAM to run a model that taught itself how to do quicksort.
Would it be possible for browsers to support this? Is it not currently the case due to some constraint? What would be that constraint?
Meditation; checking in with myself; drink lots of water; focus on personal development; self-debriefs via voice memo; physical fitness; yoga; self-expression, communication and assertiveness; good diet; avoiding too many toxins: alcohol/caffeine/tobacco/processed foods; do stuff I like; always find a way; win from any position; focus on choices and responsibility not playing the fake-victim; celebrate wins, enjoy moments, have laughs; :) fitter, happier, more productive--haha last one kidding!--I'm not successful enough to be a cynic :p :) xx ;p