skysight-inc/HackerNews huggingface dataset:
Except there isn't much to begin with, and what's there is very selective, it isn't continuous, it is hidden in a gigantic pile of muck, and it isn't verified, nor written in an accessible way. Civil journalism doesn't exist at the correct scale and organization required, and never will. That was one of those ridiculous internet pipe dreams.

National news is also diminishing. There's considerably less hard news, and more touchy-feely background stories.
One can go that way, or use one of the middleware engines that has support for Metal for several years now.
The issue I encounter is the overhead in setting up a repeatable, easy-to-use dev environment, and working out the bugs locally before I push to a prod-like system.
I don't need support, I have fixed the issue, but I know hundreds of people was affected by this yesterday, so I was just curious :)
jcs has a very nice series of Classic Mac programming videos, he writes programs in Think C 5 on System 6, on real hardware: https://jcs.org/system6c

He even made a version control system for the Mac called Amend, and a website to share Amend repositories, called AmendHub!

I'm also working on my Mac Plus under System 6, but I haven't finished any projects that I could share.
Quickly resize a video with FFmpeg/Vaapi for Mastodon
I don't see whats funny about my statement. Please elaborate on your definition of monoliths vs scalable microservices.
> If you write your project in CUDA, you'll wish you'd used OpenCL.

Only if one is stuck in a C for GPGPUs mindset.
> make sense 5% of the time

Micro-services were invented by an outstanding software outsourcing company to milk billable hours and offload responsibilities in large org.

If you want to save cost and not-that-large business, go for monolith-first. Keep it modular.
It would be interesting to see how a general-purpose AI like GPT-4 trained on internal corporate knowledgebase would perform.

Theoretically, such an AI agent would know your internal policies, biases, guidelines. It would also have more knowledge about the company than any individual worker, collating data from across divisions.

In large corps, the silofication of knowledge is a real problem. But an AI agent trained across the company's functions would not have this issue.
SEEKING WORK | CENTRAL EUROPE | REMOTE

Fourteen person team of developers + 2 PMs + 1 QA + 1 designer, focused on the
development of web and mobile products,
custom integrations and services.

Working with EU & USA clients from funded startups to corporations (Fortune500)

Can work as an outsourced team or cover the full product development cycle.

Email: info [at] higroup.si
Design and development portfolio: https://penic.si/
Website: www.higroup.si
Rate: Either fixed per project or $55/hour;

-----------------------------------------------------------
Location: Slovenia, Ljubljana, European Union
Frontend: HTML5 (Bootstrap etc.), CSS3 (Sass), JavaScript (Vue.js, Nuxt.js, React)
Backend: PHP (Laravel) and Node.js (NestJS)
Mobile: React Native
Databases: MySQL, NoSQL, MongoDB
Platform: AWS, Azure, Oracle
Integration experience: Stripe, Mollie, BigCommerce, GraphCSM, Directus, DotDigital ...
-----------------------------------------------------------

We always listen to the needs and wishes of our customers when advising on product
realisation, we can proudly say that customer satisfaction is our guarantee.

Pangea -> https://www.pangea.ai/vendors/higroup/
Clutch -> https://clutch.co/profile/higroup
There are two payments.

First you pay to participate in the lottery. This is money you've lost no matter what.

Then if you win you pay a second amount for the permit itself.
I wish this was a good condemnation of microservices in a general use case but it is very specific to the task at hand.

Honestly, the original architecture was insane though. They needed to monitor encoding quality for video streams so they decided to save each encoded video frame as a separate image on S3 and pass it around to various machines for processing.

That is a massive data explosion and very inefficient. It makes a lot more sense that they now look for defects directly on the machines that are encoding the video.

Another architecture that would work is to stream the encoded video from the encoding machines to other machines to decode and inspect. That would work as well. And again avoid the inefficiencies with saving and passing around individual images.
I mean, big media companies (e.g. Disney or Nintendo) specifically seem to believe that copyright should give them the right to basically rewrite their own history however they please - e.g. by "un-publishing" old movies or shows when they would conflict with a planned re-release of the same franchise.

That's a desire that IMO directly conflicts with society's desire to keep history. So as long as we have powerful groups that specifically want the ability to erase parts of history, historians will have a bad time.
It feels somewhat analogous to the calculator, except a million times more impactful because of the breadth of fields it can apply to. The times I go to a minimart type place and cashier laboriously, and slowly, whips out a calculator to determine how much change to give when paid 100 for a 32 cost item. Now imagine that analog generalized to basic knowledge and competence itself.

It's kind of ironic because each one of these steps forward towards making knowledge egalitarian tends to do the exact opposite. Same thing with the internet which was going to democratize knowledge, information, education and more. And indeed it absolutely has, but 99% of people don't take advantage of it - so the 1% just pull that many orders of magnitude further ahead.
To get to they point of worrying about the historians of the future we need to first get to a future with historians.

The demise of local news is symptomatic of a less diversified, a de-localized digital society that practically operates in a single unified space.

Somehow we need to make sure there are healthy ecosystems of locally bound "screens" that capture the local affairs of people.
I can just note that our Angular code seems to be much harder to maintain than our React code.

The React ecosystem also improves faster (yes, sometimes a bit too fast).
Tongue in cheek, but

> Amazon Web Services, Inc. is a subsidiary of Amazon

So it’s technically another company.

Another comment seems to confirm this akshually comment ^_^’

https://news.ycombinator.com/item?id=35812230
I'd like to see this too, but it's quite unlikely (it could have already happened with WebGL), the developer experience won't be much different than writing a native app on top of one of the native cross-platform libraries (like SDL2, GLFW or - shameless plug - the sokol headers).
That's easy: we'll make the ultimate build system! It will scale, and maintain packages, and compile all the things transitively. Just give me $xx million dollars and a few years, and I'll give you the perfect solution.

Just press this button to start the upgrade build and....boom! 10,000 services and their dependencies being built on a ton of hardware; we can practically gurantee your change in dependency will be checked... Whoops, turns out your one dependency change cascaded into about 1.5% breakage....no, I don't know who owns those packsges; why do you ask? That's not my job!

/s
Caused by how Khronos mismanaged OpenCL.
Using violence against people that disagree with your politics, or people that attempt to document your authoritarian violence is not “reacting to power”. It is power. You know this. I know you know this. Let’s not pretend otherwise.

You don’t need to ask me what antifa is beyond ‘fighting fascism’. You know that too. Stop pretending you don’t or that you’re being respectful, it’s very clear you’re not. You understand the DPRK analogy. You know who antifa is. You’re too intelligent not to.

This is “negative”, or as normal people would put it, bad. If you think using words like “negative” makes for intelligent discourse, you’re not correct. Likewise mentioning your ‘studies’ is still the ‘appeal to authority’ logical fallacy.

Honestly judging by ‘studies’ (not degree) and ‘I have revolutionary optimism’ I feel like you’re in high school.

There’s a great chrome extension that lets you block people on hacker news. You’ll think I’m going to use it because your arguments are strong, but I’m using it because they are weak.
Passkeys as implemented by Apple/Google has serious limitations – your credentials are locked into their platform and tied to their online account (iCloud account or Google account). They won't let you use your phone as a FIDO2 authenticator via 3rdparty apps (like 1Password or Bitwarden). Your credentials are only as secure and reliable as their online account services are, and they are subject all the risks of state/corp spying, forced logins at cross-border transits etc.

The dangers of this are quite clear – if you get banned or locked out from your iCloud account or Google account (this is known to happen – with no appeals process), then you lose access to all your passkeys immediately. If you are forced to reveal your Google or iCloud account credentials under threat, you have effectively handed over all your credentials. There is no way to disable cloud syncing of your credentials.

By not allowing 3rdparty apps to speak BLE/NFC CTAP2 protocol on their phones, they are effectively crippling the phone you bought and paid for to be tied to their online platform more deeply.

They have turned a supposedly open standard that is FIDO2 authenticator (as described in the white paper) into a platform-lockin product called Passkey.

One excuse for this could be that there are risks to giving 3rdparty apps permission to speak raw BLE/NFC. But that doesn't need to be the case – CTAP2 authenticator protocol could be a platform component and it could be its own specific permission that can be given to apps that qualify it (there are special privileged api permissions like that today in platform already).
Also they might be actually be different legal entities.
The subtitle is "The move from a distributed microservices architecture to a monolith application helped achieve higher scale, resilience, and reduce costs."
And the article itself mentions the 90% cost reduction.
So the title seems pretty much in-line with the original intent.
Skeets
The iPhone already accomplishes this pretty well in my experience. You can go to Screen Time > Content & Privacy Restrictions > Content Restrictions > Web Content > Limit Adult Websites. It blocks everything, including porn subreddits.

I assume they use some kind of regex to do this, and it works.
Yeah, the humour of the author is pretty enjoyable.

The tool written to redefine symbols in a COFF file is called "coffsyrup" :)
https://github.com/taviso/123elf/blob/main/coffsyrup.c
How quickly they will be adopted will be almost completely determined by how convenient they are to the user, not how secure they are.
The only time it makes sense to use edge/serverless anything is lightweight APIs and rendering HTML to end users so they get the page loaded as quickly as possible. That's the only use case good for edge. And any supporting infra that can help deliver rendered pages asap (like kv store on the edge for storing sessions, lightweight database on the edge for user profile data, queues etc). Anything that requires decent amount of processing should not live on the edge/serverless. It defeats the purpose.
Yeah completely insane original design. A design I would expect from a first year intern who is just trying to make his first project work and is picking random technologies to string together.
Additionally given how Long Peaks went, had it not been for AMD giving Mantle to Khronos, they would still be arguing to this day how OpenGL vNext was supposed to look like.
> I'd be surprised if this doesn't get taken down as it casts AWS lambda in an unfavorable light (and rightly so).

The article mostly lays the blame on step functions. Also, lambdas are portrayed as event handlers that don't run relatively often. This means long running tasks that are ran occasionally, or events that don't fire that often. Once throughout needs go up or your invocation frequency comes closer to the millisecond then the rule of thumb is that you are already requiring a dedicated service.
There's a lot of room for "chinese-room" automation:

Write a verbal description of your cloud function and let the LLM simulate the execution.

Very cheap to develop. Very expensive to execute.
> the deeper motive is more about invading customers' privacy by getting hooks into their phones

They just do it because it's easier. No menus to print and update every week or however often. Out of salmon today? Just take it off the menu with a few clicks. It's easier for the same reason that most of us would write a letter in Vim or Emacs or Word or whatever and not on a typewriter.

I dislike this trend as I almost never carry a phone and even if I did an A4 menu seems loads easier than a 6 inch screen, and any half-way decent restaurant should just print a menu because it's not that hard or costly, but there is no secret motive here beyond that it's just a bit easier for restaurants.
This is astonishing coming from Amazon.
I'm just grateful a language like Java has any sort of namespace solution to dependency nightmares.

I have lost track of how many times I did a git pull on a Python based solution only to find I broke all the things when I tried to upgrade one package.
On the other hand, there are fpga boards priced comparably to microcontrollers now. It can be very refreshing and useful to escape the "programming" paradigm.

Hobbyists are already contributing the value of their time which is generally much larger than the cost difference between device types, so in a sense the fpga barrier to entry may actually be higher for companies than individuals at the moment.
This is what they do with The Wave.

I believe they allow 20 per day. 10 are first-come first-served and 10 are a lottery you can enter for a few dollars in advance.

Seems pretty fair to me.
There are mpsoc ultra scale+ chips that are under 100$ these days, so I think that's not true anymore. Even low end mpsoc ultrascale fabric is way better than that old altera stuff, with lut4 clbs, ultraram, and better dsp blocks. I've had the fabric run at 500 mhz in my designs.

https://www.avnet.com/wps/portal/us/products/avnet-boards/av...
If you really want to upgrade, just try it out. Don't worry. MS' CPU requirements are somewhat arbitrary (presumably they want them to include spectre/meltdown mitigations) but they are not strictly enforcing the rules. This is probably just to protect them from lawsuits. So far nobody reported, they were not receiving any more updates bc of their CPU.

I also recently watched a nice explanation of how to install/upgrade Windows 11 on a non-supported machine: https://www.youtube.com/watch?v=UL_maCWM5bk&pp=ygUTZXhwbGFpb...
The entire library is so spread out, with so many half-assed features.

When I wrote Angular I spent 2 weeks on getting something similar to `props.children` working. <ng-content> didn't work if the elements were dynamic. Outlet system was way too verbose.

The 2 way databinding is anachronistic and belongs in 2010.

The i18n system they shipped with is awful. No way to have translations in code, only in template. This breaks down very fast when building generic components.

The DI relies on https://www.npmjs.com/package/reflect-metadata, which makes the builder an opaque black box unlike a webpack configuration.

Because of the opaque CLI I've spent 2 weeks figuring out why every third dev build resulted in a 150 line long tsc stacktrace, and it turned out to be angular's 1.x types package. Would have been so much easier with a webpack configuration.
With various levels of works, and Android drivers don't get updates, so in those cases most likely Chrome will blacklist the drivers and offer no support.
Yes, Self is very cool--I've read about it before.
I built a little microservice on the side of my monolith for PDF creation. It used headless chrome and ghostscript to render html to a nice PDF. The problem I had with having that code inside the monolith was that it increased my docker image creation for deploys by a lot. And that code pretty much never changed anyway.

I did feel a bit embarrassed having to make a microservice after having argued against them so much over the years. Hopefully I can stop producing PDFs soon so I can delete the entire thing :P
And vastly improves security!
Microservices works better if you don't trust other team. While having trust seem like a basic thing, this is absolutely not the case for a lot of companies.

With microservices, it is easy to see services which are down or have high error rate or latency, have clear API contract and call out the team for breaking API contract, and assign cost for which the teams have incentive to reduce, or at least not increase it.
> the fascination with occult forces really has not aged well

Just wait… so much of it is not what people think it is.
To be able to observe their reaction to unknown without confirming I am there.

And maybe I don't have unlimited sensors - so I want to see as much detail as possible.
SolarWinds: The Untold Story of the Boldest Supply-Chain Hack
GPT-4 Eyes
- Because we are innovative and it's the future! /s
It’s not really about how people are treated by the characters. It’s about perspective taking and relatability. 50 Shades is written by a woman, from the perspective of a woman, and it’s about her fantasies. Why wouldn’t women respond to that?

What turns women off, in fiction, is seeing other women through the eyes of a male character. You can’t identify with a character from the outside like that.
This right here is one of the reasons I got out of software development. Not micro services in particular, but just the unthinking application of some new pattern to everything.

Everyone wants to do the new cool thing. Everyone wants it on their CV. To be followed some years later by everyone saying how awful it is, and moving on to the next fad. Rinse, repeat, round and round we go with no actual intelligence being applied.
Customer doesn't know their own requirements?

Your job is to figure out what they actually need even if they don't understand it?

Seems pretty par the course.

There are dozens of reasons to migrate to the cloud. Do they apply to everyone? No. Are they always worth the cost? No. But the whole "cloud vs not cloud" argument that happened, got settled ("cloud"), and is now being restarted by the DHH-like is not data-driven and full of exaggerations and fear-mongering from both sides.

Then you add on top of that that the main product of moving to the cloud is "operations" which is typically measured in "hours of human capital being impacted outside of core working hours". When the market is booming, tech humans are expensive and fickle, and don't want to undertake more operations than they should have to, and companies are forced to pay cloud providers.

But in today's 2023 climate, any company looking around to decide how much to spend on cloud just says "Why would we pay for something when we can just ask our engineers to work more hours, and invite them to quit if they don't like it, oh wait nobody else is hiring anyway"

No cost calculator of $$$ saved considers that overtime is free in our industry.

tl;dr the cloud backlash is overblown, more companies/businesses would benefit from cloud than not.
That doesn’t make a lot of sense.

If you give poor people money so every can equally bid on the auction, then why not just make it a lottery and not bother giving poor people money they’ll just give back through auction?
> React has a lot less going on.

I don't think that's quite true anymore. As someone sarcastically remarked on Twitter [0], React has patched native events with synthetic events; has rolled out its own scheduler in order to achieve the suspense effect ("patched the event loop"), and is going to patch the native fetch for reasons that I am not clear about, but that are doubtless also suspense-related. With hooks, it introduced a syntax with a set of implicit conventions that, confusingly, still looks like javascript, but has significant differences from how javascript works ("the rules of hooks"). React provides its own way of lazy-loading modules; its new server-side renderer currently assumes that when React rehydrates, it takes control of the whole DOM tree; and the docs are now strongly recommending people to use full-fledged frameworks (Next, Remix) when starting new projects. React has long outgrown its "it's just a library" stage, sadly.

[0] - https://twitter.com/RogersKonnor/status/1618739256775815168
I bet it will replace Vulkan for most people who would otherwise have no other choice than using Vulkan on Linux or Android (these are the only operating systems where there's no alternative modern GPU API than Vulkan).
Not from USA, but my opinion on raffles vs auctions:

Raffle is not giving them money. Raffle is giving them a chance. No matter how much money you give to poor people, rich people will always be able to afford to outbid them.

So sure, giving money to poor people (or better jet, making sure they get decent pay in the first place) is good idea.

And raffle makes sure, prices stay reasonable so that even poor/middle class people can on occasion enjoy the parks.

You do auctions when you want to maximize profit.
You do raffles when you need to rate limit access to a limited resource.
Solution looking for a problem
If you came to me with a design that included passing individual video frames through S3 instead of RAM I would honestly think you were joking. What a wild article.
That the initial version of WebGPU doesn't support a specific feature doesn't mean it won't be supported in extensions or new versions down the road though.

(most current restrictions are enforced by the requirement to also work on mobile devices)
Especially now that it's on the frontpage of HN :-)))
Do you mean to say simulations and models have good tests? In my (very limited) experience with scientific computing that's absolutely not the case. There's a decent chance the software is impossible to test because it can only be run all together and is nondeterministic.
Depends if you're counting all the WordPress level projects. Then it'd be 0.01% Vs 99.99% I'd imagine.

But that just puts into perspective how silly this argument is because I have no idea what a project means to other people.
The title makes it sound like Prime Video abandoned microservices all-together, but in reality they only did so for a single service.
I can't even fall asleep while feeling the thing on my face :-(
Are people who have been given the information that they're using a placebo trully convinced of that or do they just have a mental barrier preventing them from further acknowledging it and just resign to respond: "yeah, I know it's just a placebo"
It’s depends on how you slice services. For one micro-service per a team I see benefits. On another end of the spectrum a single team managing 10-20 micro-services with more than one service per developer. IMHO it creates more problems than solves. Also it is usually a waste of HW resources because a library call it is cheaper then a network request.
You don't have to use all of that though, it's optional. A fairly basic but serviceable HTML document that looks decent is still pretty easy.
This is the best start of the morning!
Lovecraftian subgenre monsters (52 min)