skysight-inc/HackerNews huggingface dataset:
DDR5 isn't such a problem for fresh builds, but for example, I already have 64GB of DDR4 so I'd rather use that and let DDR5 improve and have prices come down further before switching, so Intel is very tempting (not that I strictly NEED to upgrade) as I'd only have to upgrade CPU and motherboard.
Nope: those are not anonimized nor real time.

Basically, Google knows a road is congested by having dozens of people (with their Android phones and location services turned on) slow down on a road where they would usually go much faster.

I want the same thing with better privacy guarantees and that's open source and free to use.
I'm going through this right now. At dayjob we have a lot of internal dependencies and libraries that are created sufficiently far from me that I treat them as third party and when things go wrong (which they do a lot) it's a nightmare to debug and work through. Easily half a day gone.

So for sideproject I'm going mostly bespoke and using very little 3rd party libraries. The result of that is there's sooooooo much boiler plate to write and it's very boring and it's hard to be motivated and productive to get through it. What's keeping me going is that once the boilerplate is done - it's mostly the foundational level of data queries + endpoints - then I shouldn't really have to touch that stuff again.

My conclusion is that there's no great answer.

Using lots of libraries is like riding a horse. It'll start moving right away but you don't have full control and you gotta find the right way to get it to do what you want, and may have to fight it if it really doesn't want to. Vs building most things yourself is like building a car. You don't go anywhere for a long time as you're building it, but once you've built it you can move very quickly and if anything goes wrong you can easily pop the hood and fix/change things up.

I think for long lived projects it's better to build the car, but also be disciplined in writing very good code + documentation. The initial build out sucks hard but that pain will get amortized over a very long future and ultimately be worth it.

And for absolutely required dependencies go with paid services. Specifically paid services where the company's primary focus _is_ providing that service. They are financially and existentially motivated to give good service, and are usually good about keeping backwards compatibility while usually staying on top of security/modernization upgrades without requiring work on your own end. A managed database is a good example of this kind of paid dependency.
So, CERN doesn't run that many machines. They do have that many cores across their OpenStack fleet. I actually think it is even more than that now since they've tweeted graphs[1] from adding 800+ new physical nodes to their clusters. Anyway, it is not all about CERN, but they are an active community contributor. They are an operator who speaks publicly of their work, challenges, and successes. They have championed fixing some issues they have encountered at their scale, and provided feedback to the various projects on aspects which would help them solve their infrastructure automation issues. The same has occurred with the telecoms and other verticals with specific needs that cannot use public clouds.

As for docs, they vary from project to project, but one aspect I've encountered as a frustration and heard large scale operators echo, is that often search index results seem to favor some older specific release as opposed to the latest release, which creates a lot of confusion if your not aware of it and don't see the warning on the rendered webpage. Some other popular open source projects have encountered the same exact challenge, and it is a hard need to balance.

[1] https://twitter.com/ArneWiebalck/status/1478778715005984772
So have a max file size.

Also, the same ToS applies if you use the paid product. Unless you buy an additional addon for non-web traffic.
Work less doesn't mean less productive. This article has practically no substance and has nothing to say. It's as if this was written by a bot.
We need web3 to unbreak the web.

Hear me out before you rage-downvote me. “Web3” most of all means a functioning identity model that is platform-independent, user-owned and thus scales the solution to the bot problem beyond the limitations of a single platform.
Can't the exact same argument be made for code, though?

"That didn't work, and the traceback (if I read it) isn't very helpful. Guess I'll try something else I found on SO."

You learn ops by doing it, preferably in an environment where when you inevitably do it wrong, it doesn't break prod.
I am aware of voice memo apps running a library like vosk transcribing just fine on device instead of in cloud and without cost.
It's because often your software engineers know software development and just enough administration and operations to be dangerous, and your administrators know operations and just enough software development to be dangerous.

Letting them wade into others responsibilities often introduces a lot of that danger.

System administration is an entire discipline with a history and way of thinking and approaching problems at a systems level. Software engineering is the same, but with an approach that often emphasizes handling problems in the application.

Letting solutions be put into applications that are best handled at the system level (where system isn't just an OS, but might be a complex network of them), or put into the system when it could easily be handled by the application, caused inefficiency and problems.

The solution is to either hire only very accomplished people that can do both and make the right decision of where to put solutions, or hire people that can do one or the other and put them together with a few (maybe one) person that has a good grasp of both and can make executive decisions when the right time and place is for specific solutions (an architect).

The latter is easier to hire for.
I looked for the 22.10 download a few hours ago and didn't see it so I did a Google search and found today's comment about it possibly being delayed: https://askubuntu.com/questions/1436351/when-will-ubuntu-22-...
That was when things were getting hyper-partisan (they still are).

There were a bunch of Democrats and liberals, that were saying "I wish Galloway could be President!"

I'm like ... no, you really wouldn't like that ...
Stripe Takes Steps to Prune Workforce
> I have bewilderingly tried to discern why software development continues to grow more and more complex.

It's because of growth, software development today is both simpler and way more complex than before and that's entirely due to growth in the sector. In many ways it's simpler than it ever was, I'm writing an API using Lambda/API Gateway in AWS and it blows me away how quickly I am able to get services stood up and configure my API. But in another way it's so much more complicated, for this same API I spent 2-3 weeks experimenting and researching IAM roles and how all my AWS resources would interact with one another.

I would say the floor of software development has become way simpler, deploying a site to Netlify is way easier than dealing with webservers of the past. But while the floor is lower than ever before, the ceiling is in the stratosphere, with extremely complex systems that you can string together in the "Public Cloud".
Articles like these are simply crap. Commuting less != working less. If commuting is work then employers should pay for it or have the time taken to commute deducted from work hours.

Either way articles like these are horseshit and likely sponsored by those renting human farm space (offices).
No way in hell you could buy even a small building in the city for the stated purpose of homeless services for anywhere near that amount of money. Anything homeless “attracting” will have you swarmed with NIMBYs and red tape for years. It will be called a crime magnet. People will say that it will reduce property values. They will sue you to stop the project. The one thing everybody agrees on in the public review meeting is that the place to put the homeless is “not near me”. You will spend way more than $1.7m on lawyers alone for a project like this.
Yes you should, buster.
Same, so I use nextdns.io for ad blocking on my ios devices.
You hire those engineers and then you have them implement and support Continuous Delivery for your business, yes? DevOps is a silly term, but one that companies seem to use for "infrastructure engineers who help us continuously deliver value to our customers, efficiently and pain-free". Give your people whatever title you feel comfortable with - but essentially they are "doing the DevOps". :P
> If there’s a way of leveraging it effectively...

Those ways are quite heavily constrained by needing to start with what is already available, and for each step to be both heritable and reproductively advantageous.
> When was the last time you saw a product manager high-five the ops person and say, ‘fast fucking autoscaler!’?

That's me. I did that.
Yeah, setting up arch for the first time takes time. For newbie users it is definitely not appealing process, and also I would not recommend it. It's not a long process, but you do everything yourself and all this in the terminal (no GUI installer).

I learned a lot about linux when I decided to try Arch. And as OP, I also never looked back :)
> No public restrooms, no chairs in Starbucks, covers on everything in Walgreens, ID requirements to enter stuff, you get the idea. There's no obvious solution to that.

Is this seriously the reality of SF? Never been there. If yes, that's pretty bad and degrades the city in some aspects to 3rd world place. But then again I am in Europe, many things like crazy homeless people I saw often in LA are unheard of here.

What do you do if you do multi-hour walk around the city? Or hop from one restaurant/cafe/bar to another one?
She doesn't impose multiple business-critical schedules on that, so you can just wash them, pick your nose for a while, take out the garbage and go play games. There is nothing wrong with doing related jobs solo when situation allows, but this example is also far from learning and using "modern" full-stack of stacks or doing surgeries.
Send a link, would love to try it.
Is a country a democracy if people are blocked from voting because they are female?

Obviously democracy is a sliding scale, but what was in place in the 1800s had a lot of headroom.
This is another power imbalance that is so frustrating. The account was “permanently suspended”, which you think means permanently suspended. But that only applies to normies. All the words are meaningless if twitter says otherwise. It’s really like living under a medieval king who is a law unto himself.
For me it is just Firefox that I don't want in snap form. The Mozilla team still puts out a .deb version via PPA [0]. You should probably also pin to this source so that the snaps don't get installed [1].

[0] https://launchpad.net/~mozillateam/+archive/ubuntu/ppa?field...

[1] https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-d...
SaaS model requires software to be always online (strict sla) and you need to be able to update it without downtime or very little downtime. That’s the reason. For example, telecom software that always had these requirements was always complex
I assumed it was an attempt at ideologically shirking accountability for the outcomes involved in elected officials doing what they were elected to do.
My twitter evolutionary art bot @tweegeemee is going through a fiasco like this, but I don't have nearly the same presence as Ben.

The account was suspended for 10 days and I'm still trying to get the app (separately suspended) that runs it unsuspended...

They must be going through some kind of crazy time over there between nation-state trolls, the Musk fiasco and the run-up to midterm elections. Yeesh.
I suspect the biggest TCO item for this, at least in Europe would be the energy costs over 5y. Even worse if you chuck an RTX in there.
It just makes life more difficult. It's work in a way, dodging all this.
"and the fact that I tried that right during the Python 2->3 conversion didn't help either"

The huge and painful Python 2->3 transition could not have come at a worse time for OpenStack adoption. I believe it's one of the major reasons why OpenStack was found to be difficult to use, brittle, and documentation not up-to-date.
Your guess is as good as anyones at this point. There’s just many over corrections that resemble strong levels of grandstanding. React is complex? Okay, let’s ditch JavaScript and just do basic server rendered pages.

It’s a laughable over reaction (pun unavoidable).

These are manic states the dev community enters, and all pragmatism is lost in our discourse on the solution.

Cooler heads are not prevailing. There is certainly a solution in the middle.

Devops is bullshit is also an over correction. It’s worth saying that making infra more accessible is a democratization of that entire sub-field. How do we preserve the good part of that?
Would you mind sharing the company name? That sounds like a lovely model of employment. After getting used to my own espresso setup at home, I don't think I could work at an office without at least a decent machine (about as first-world a problem as it gets, I know).
it's really not that complicated. PL2 is two settings in most bioses, a power limit and a max duration for that limit. sure, you could spend hours optimizing with all kinds of tweaks, but if you just want your cpu never to exceed 150W for more than 120 seconds, it takes a couple minutes to configure that.

but that's kinda missing the larger point. if you care more about power consumption than performance, you aren't the target audience for K-suffix parts anyway. these parts are specifically marketed to enthusiasts.
Yes - comparing the above 65W score from AMD to Intel's 145W score highlights the stark difference!
Which seems logical to me.

Though there is an issue that some of sqlite's own functions are unaware of this and will end early if a NUL is encountered: https://www.sqlite.org/nulinstr.html
Hard disagree but Mandy Rice-Davies applies.

Some interpretation of DevOps may be BS, e.g.

>> Need a database? File a ticket with DevOps.

That does seem like a bit short of the mark. E.g. that should be automated provisioning in 2018, never mind in 2022.

Counter points as to why DevOps is not BS:

Today there's just an acceptance that you version your code in VCS, it wasn't always that way. "Hey, this doesn't look right, i know you said you based your change on gui-app.latest-final2.zip but was that Steve or Laura's version of latest-final2?". If you didn't work through this period you'll struggle to believe how common it was for shipping products not to be fully up to date in VCS or not to have VCS at all. DevOps changed this.

Continuous integration? No there were people hired as "merge masters" or "build managers", i promise i am not making this up. DevOps changed this, the idea that you wouldn't do at least CI or perhaps CD is unexpected today.

Deployment automation? Sure, you email it to the ops team, send a few more emails with attachments late on Friday with ammendments and hope that they deploy the right one. Automated deployment as far as the developer was concerned. The ops person on the other end? Sure they had a batman's belt full of hand crafted tools and scripts but it was definitely pets not the cattle DevOps has made us strive for.

Testing automation? The testers sit on level 3 not next to dev on level 4, there's about 4 banks of desks over by the cupboards, that's all the testers. They have lotus notes databases with checkboxes to confirm when they test something. If they find an issue a regression report will arrive with the dev team in under a week.

I could go on an on. Platform teams are great when used correctly. You can say something similar about DevOps.
GWAS is a very limited technique. Most people in genomics still have very simplified models of how complex organismal phenotypes are formed. My goal was to build an embedding between genotype and phenotype that had predictive and generative abilities. Based on everything I've seen, a few tens of millions of genomes for a few hundred highly specific molecular phenotypes is definitely doable if you had all the world's genomics data at your fingertips.
Theres an actual phenomenon known as bitrot, where over time, copies and storage, files degrade by having their bits flip. This can apparently accelerate during the process of a file being transferred (whether from the internet to a drive or ram or to a drive or vice versa), bits can be misread because of the speed and breadth they come in at. Ecc prevents this.
>>the only alternative is to start making CPUs by hand

Agreed. For some applications the cloud difference is significant; for many (most?) others though, "Cloud" is just rebrand of "Hosted". And even for more cloudy offerings, while I'm in a very specific and different part of IBM, some of the old timers/architects/powers-that-be keep trying to explain "We had that in 1969!!!" :-D

Agreed also at rewriting of history when it comes to development/support/operations models. My dad has been IT director and he chuckles when I talk to him about "new and exciting paradigms" which he of course sees as turning a circle to what they had in 70's and 80's :)
The Competition Commission of India, which began investigating Google several years ago after complaints from local firms, said in a press release that Google requiring device manufacturers to pre-install its entire Google Mobile Suite and mandating prominent placement of those apps “amounts to imposition of unfair condition on the device manufacturers” and thus was in “contravention of the provisions of Section 4(2)(a)(i) of the Act.”

It also ordered the Android-maker to not offer any incentives to smartphone makers to exclusively carry its search services.

... The antitrust watchdog said in its statement today that device manufacturers should not be forced to install Google’s bouquet of apps and the search giant should not deny access to its Play Services APIs and monetary and other incentives to vendors.

Good. Ensuring monopolies don't crush competition, and creating a level playing business field is what prevents capitalism from becoming dysfunctional.
100% agreement. Agile and devops have done more to wreck software development than anything I've seen in more than 30 years in the industry.
It's absolutely a balance, but I've seen it the other way too. Devs spending weeks to make something more efficient when compute time costs cents.

That has a minimum cost of their hourly rate. The maximum cost is the cost of not doing what's most valuable to the company.

> In 2019, Lyft spent $300M on AWS [1]. Sure, it's a big service, but are you seriously telling my that it's necessary to spend $300M in a single year?

They didn't spend that in a single year.

It also depends what they were doing, I was recently very shocked by the data costs of a major hardware store in the US but after breaking it down it made more sense. It all depends what they get for that $300M over 3 years.
> a far better option than actually trying to provide housing or attack more of the root causes.

I see a lot of discussion among urbanists of "induced demand" when adding extra lanes to highways. Are we sure there wouldn't be induced demand from providing free housing to the homeless?

Already, the Bay Area & LA are major draws to homeless populations throughout the country. [0]

[0]: Yes, there are some studies that show "70% of homeless people in the Bay Area list most recently becoming homeless in the Bay Area" but many of those people came to the Bay in the first place to access homeless services and that study also relies on a very expansive definition of homeless). These studies are also incentivized to show this as a local issue from an ideological perspective. If you actually ask visible homeless people on the street where they are born, most will not say the Bay Area.
Never?
Unless you give up on NFC, banking apps and all those goodies.
San Francisco, the government, owes the constituents it's meant to serve, and whom pay its taxes, literally everything.

San Francisco, the city and community, as a society, owes what anyone in the world owes everyone else: an ethical existence.
Just say "No" to these work-a-holic junkies. Don't open the article, don't read the article, don't engage it any further than "Nice try Mr. Capitalist"

Anyone writing these articles is a Fed. All of these article are just trying to guilt trip and shame people into working more.
> none of my employers so far has paid me to commute so I do not consider it working.

Yikes, do you apply that same reasoning to slavery, or is it only your own time that you consider worthless until paid for?

re: makeitrain -- you don't work for Amazon, then?
yep! https://www.moderntreasury.com/journal/rss.xml

You can also get automatic emails
UK Commons passes bill to electronically tag protesters without a conviction
> You have people who build stuff without caring where and how it runs.

In the old days, developers would also configure the design of the system it ran on.

"Alright, we're going to use some fast CPU front end nodes with smaller, faster disks, and then have a load balancer, our database server is going to have the most RAM, now let's set these resources up on a CDN to serve faster, this memacache server is really going to lighten the load..."

I think the idea was to use tools that automatically did all this work for you, but it just ended up creating another tier of people that configure this side of it.
I'm not familiar with mobile app review process, would any change in code require a re-review/re-submit? If Google approved it as-is, could the developers add a few lines as an "update" and skip over the full review process?

Seems like the ruling is being made on what can be done with the current permissions, rather than what is being done. If that's the case, I sympathize with the devs but I think I support the position Google is taking there.

Off-topic comment: I use NoScript, and the entire text of the article renders for a half second before disappearing and for some inexplicable reason requiring JS to be enabled. If you can render it for that half second, why hide it? Why force me to use JS when you just proved that you can render it without?
> If you're already wasting sufficient amounts of the requisite elements as waste products of some other thing you're already doing then finding a way to bond those elements and then burn the resultant compound for rotary power may be more economically efficient.

Your sentence is a bit vague, but "some other thing you're already doing" sounds like petroleum refining, which is precisely what we need to do less for use as a fuel. Also, ammonia created from petroleum isn't being wasted today. It's used for making fertilizer, and the whole process has a high cost in CO2 emissions.

When the time comes that we have so much carbon-free energy that we can afford to use the excess to generate ammonia, we ought to use it to displace petroleum based ammonia for fertilizer. There may be a few niches (ocean shipping) that require a liquid fuel like ammonia, but it makes little sense to use it for ground transportation. If a liquid fuel is required, things like sustainable biodiesel make more sense.
Why would you have a dev team who has used mongo before and is comfortable with it move to a different DB?

Serious question.
Large-scale gene study identifies DNA variants linked to dyslexia