Oregon just passed something like this I believe. We basically charge data centers 30% more for power.
HN user
oooyay
https://ooo-yay.com/about
mailto: m at ooo-yay dot com
No one ever cared about DCs before now.
Society hasn't felt the very real effects of data centers until recently. Power supply being short meant that residential customers have had to pick up the tab for heavy industrial users. We've started to learn just how bad all those dams we built are for the environment and many of them are tied to data center money. Elon Musk waltzed into Memphis and stood up a natural gas data center that has basically poisoned the surrounding area.
Maybe nation state actors are helping, that can always be true. It is also true that the American people are starting to realize they've been had many times over and are just starting to ask for a better deal. I think we should listen.
I'm not saying it's a bad choice. Slack is written in Hack, Discord written in Elixir, and Teams is written in C#. Why teams choose languages is always a point of curiosity to me.
Disclaimer that I used to work at Slack
I love that we're challenging the status quo in chat. It feels like we've settled into an eternal September of sorts. I am somewhat bearish that Slack and Teams will survive, or rise to, the agent era.
That said, I'm curious whether NOSTR is really the protocol for this. For some really large corporations you're looking at a lot of clients (and their shadows like cellphones, local agents etc) as well as a lot of (likely) team-based agents.
The identity architecture makes sense for centrally hosted agents. Users also probably have their own personal agents as well. Do those just reuse user credentials or are they differentiated in some way? I couldn't tell.
I also am curious whether git really needs to be a dependency here. Like, maybe for Block it does, but it introduces a lot of complexity that I feel could be exported to merging VCS Host events to the Buzz event log.
I'm also curious what challenges will arise as new capabilities emerge. For instance, both Sol and Claude can now render native components in my chat window which is a massive leg up in terms of firming up a design change.
Rust is also a choice. I'm curious what alternatives the team considered and how they landed on Rust.
Set clearer requirements, set stricter constraints, and the solution follows. That solution is the perfect one for you, for that case.
I think this is a bit of a generous reframing of what seeking perfection is. Generally I think perfection seeking is best described as over-focusing on the details and pre-planning instead of laying a general blueprint that leaves room for pivots, future decisions, and iteration along the way. There's a whole breed of engineers that are really great thinkers but get stuck in the mud trying to pre-think the best way to do something instead of being adaptable.
Salesforce often does product announcements to determine how the market might respond before they ever build anything. The very thing they're selling may not exist and might not even be possible as they describe it.
I think it's a way some businesses just do business and the market has not issued a correction to that. Maybe it should?
Palantir is also the kind of business where every engagement is somewhat to totally bespoke. That's a big departure from a more typical SaaS model where you focus on providing a platform that your customers build on top of with a more generic set of tools.
I am curious whether this FDE direction will result in more product and platform complexity that is more difficult to unwind.
Immediate mode API in the true sense: you never need to maintain UI widgets or sync your data with widget state.
Known Issues & Limitations
The following are known issues and limitations that we plan to tackle:
Large text blocks will kill responsiveness! Use the LargeText widget.
The widget catalog is aimed at developer tooling, not general consumer polish: no rich text, tree widget, or date picker yet.
There is no robust theming system. Some widgets take an accent color; custom button styles mean implementing your own (the stock Button is a usable reference). Styling can still be verbose at times.
Are these statements compatible?Even very smart, very accomplished people can be very wrong. Xen is seeing a resurgence from Xen Orchestra and I've used it in my homelab. It's quite pleasant. I also, of course, use de Raadt's software as well.
Yeah I agree with that. I'd also extend this to ICs, but the effect is probably less pronounced as those with much more consequential power.
The individual executives I think are smart and I don't think the post discounts that; maybe "blind" is a distracting analogy. What the post draws into question, which I think is relatively common, is how a persons immediate incentives might intrinsically change a person. For instance, a very smart Adobe executive may start to pin engineers against each other to produce better results because they can and it produces results. They may begin to over-reward the few in search of inspiring the many. They may take fewer bets on the future because the status quo is just fine. All things that I think you as a start up founder would not do because you have immediate feedback mechanisms and consequences that signal that could lead to the end of your startup.
If you sat these same executives down in a one-on-one setting and went through a history of things they did and how they might've impacted people I think you'd probably discover some shame and embarrassment once they're removed from the incentive pool. That isn't to say they're bad, just to say that incentives are guides in the dark, and the inside of a massive corporate machina is full of tunnels.
also, hi TR :)
You're saying that BetterAuth will remain 100% free and open source, will continue to be maintained, and unlocked from Vercels ecosystem?
I see OP responded but I'd add on that "further" can mean product vision and pivots. When you're the only one in the room that voice is limited; even when you may have only listened to 1% of these pitches it may be the one you never would've come up with.
It can mean the power of delegation and creativity. The worst kind of teams are monocular, democratically oriented teams where every member must be on and act in the same manner. It's great for efficiency, it's horrible for productivity and creativity.
You already have a lot of replies here and the comment is provably divisive. I'll toss in that while only you can judge whether it was truly a waste of time, a lot of that factors in how you used it. If it benefited you in interview material understanding, increased the probability that you could extend your network with someone, or other somewhat intangible signals then I'd say it wasn't as much of a waste as you say.
I have no degree and that is arguably worse and there are exceedingly fewer people with my background in technology on the coast. On the other hand, I spent a lot of my career writing applications that solved Software Operations problems. I spent a lot of time working in small teams rather than huge ones, I often did not have product or project support. I used to loathe that chapter of my career because of how toilsome it was in my memory. Lately I've come to appreciate it a lot more because I am much more self reliant and I often have the skills and familiarity to run much larger teams as a tenured engineer.
Long way of saying, the value of an experience or thing is often not immediately realized or appreciated.
Incredible, Bill Hicks on HN. My life has come full circle.
Ironically Bill smoked like a chimney and for that we can also largely thank marketers.
This was really cool. I would love to play some Dave Tipper on this to see what it looks like.
Why would a carpentry shop buy hundreds of thousands of dollars of power tools without consulting with their employees to see what they actually need to get their job done more effectively? The logic of buying the tools then forcing the employees to use them "or else" is completely backwards in any sane world.
This is how it's gone down throughout history. It's why we remember the Luddites, textile workers who started smashing stocking frames and power looms because the machinery was introduced over their objections. The whole goal was to undercut the craftsmen's wages and bargaining power.
So, no, your expectation to be consulted was never going to happen and has not happened throughout history as industrialization has advanced.
I don't think Overton implied any causality between the phases of the window, just that distinct phases exist and that forces act on the window to cause it to shrink, expand, and shift.
I use Wails which is Tauri but for Go and I don't have the kind of issues you're mentioning. Maybe that is a difference between Wails and Tauri but I don't think the system WebView is a significant factor.
Yes, but what happens to the professions and classes you've mentioned that wasn't looked at in this study is that new skills developed. For instance, something was assuredly lost as programming on average deviated from low level programming, but new skills and optimizations were gained. Fewer people knew how to construct a real-time bitmap from scratch, but more advanced software was being built on average as people were armed with greater and more manageable abstractions.
I had the same experience recently. Turns out ClickHouse would reduce our DB operations by 60%, remove the need for a TSDB, and reduce query times from ~300-500ms (and sometimes ~3s) to roughly ~75ms. Lastly, and most impressively we were already seeing a ridiculous level of compression and our storage cost benchmarks were reduced to the cost of S3. This took a $2-3M storage layer down to one measured in the single thousands per month.
ClickHouse is no panacea but if you understand how your data is accessed and thus how to arrange it you will get so many miles out of it.
As in most things I think it's a mixture of quantity and set and setting.
I enjoy a yak, but right sizing my yak is pretty important to my enjoyment of it. Maybe the yak doesn't get a full shave but gets a trendy hair cut, and that's okay.
I leave my yaks at home when I go to other engineers decision meetings, project kickoffs, or RFCs.
I've been building my own IRC client: https://github.com/matt0x6F/irc-client/ (#cascade-irc on Libera)
The client focuses on extensibility, IRCv3 compatibility, and a modern UI and UX. I am realizing that IRCv3 is capable of being built on top of though, so I may start incorporating external features outside of the protocol itself.
Some friends and I have also been building a start up a month and the latest one to come out of it is medspa software: https://spaarc.net
Not even just digital; much of the world is shifting from high trust to low trust as well: https://social.desa.un.org/sites/default/files/inline-files/...
The statute requires that a person knowingly circulate a false report. Combs says she was repeating what people told her. Gregory says she should have verified it with the hospitals first
It would be a violation of HIPAA for a medical system to disclose that to a private individual. The State Health Services or TCEQ would need to conduct that investigation and ask those questions. Both of those are state level agencies and would require significant momentum for a small town like Trinidad to trigger their attention. Ironically, it sounds like her social media post and the Streisand effect around it have triggered a TCEQ boil water notice and (likely) an investigation.
It is absolutely bizarre for a municipal or county law enforcement agency to take interest in this kind of thing. Texas Rangers and federal authorities should be looking at what triggered her arrest and whatever investigation came before it. That's assuming Greg Abbot, Dan Patrick, or Ken Paxton haven't totally compromised them at this point.
What's really interesting in this comment chain is an observation I've expressed a lot more lately. When someone knows an LLM was involved they raise their expectations. I do it too in my own work and I have to remind myself things like "this bug would've also likely occurred with a human working at this level of complexity." The real question is did the operator arbitrarily and knowingly increase the level of complexity or is it appropriate for the task.
There are two simultaneous problems that I've come to understand with datacenters and the people that live in their proximity:
1. Somehow the public is always left holding the bag for increased transmission costs despite the cause of the increase being a single (or short list) of outliers.
2. The residential public, as is tradition, is always asked to scale down for industrial demand.
How can we imagine expanding a system that results in both of these outcomes? That, to me, seems to be the thing to fix first.
There's also another animal/dog documentary that I've watched recently that puts a finer point on this realization. The secret to survival and evolution is cooperation. For instance, not all dogs evolved the same way in this documentary. Some were more nuturing, some were more problem solving. For the focus of the documentary the challenge was to match the dog with a human that had a need they could address.
I think somewhat egotistically humans underappreciate how we have also been goaded by our "pets" into our own evolutionary journey. Most of the subjects of that documentary would not be alive if it were not for those dogs.
I'm not sure this is really true anymore and it ignores the reality on the ground of "cheap areas". Often times cheap areas are underserved in a way that once you require or depend on a service that is baked into other higher cost of living areas your life becomes much more expensive than if you'd simply lived in a high cost of living area. There are many examples of this but hospitals in rural areas are one of my favorite examples. There used to be many of these but many people didn't realize they were all (or mostly) subsidized capital ventures. Many of them are closing now that the subsidy has ended. So, is that county land cheap? Yes, but when you have an incident where time matters your likelihood of being cooked goes up precipitously.
I did read them but I interpreted the topic of this thread to be Anthropic's vague approach to compliance enforcement not specifically how claude -p is used and interpreted by Anthropic.