skysight-inc/HackerNews huggingface dataset:
It is true that generative ai technology is often trained on human artists' work. But how is that different from human artists taking inspiration/learning and adapting the style of other human artists? I suppose the argument is that humans should get special treatment in the copyright domain?

I wonder if it is possible to get a machine to learn a style without input. Likely a room full of typewriter monkeys searching for Shakespeare scenario, but a human would still be involved in the loop to "confirm" the desired style - which is technically a creative decision in itself.

Which I guess shows the true nature: machines could generate stuff for machines without any external input. But we built them, so we've tasked machines to generate stuff for humans. And therein lies the answer I guess.

I 100% believe machines can be creative. Creativity isn't something unique to humans or to living things. For me it's a concept.
When was that? I am so glad that for the past 5~6 years every contract I have worked has had unit tests and for the past 10~12 every place has at least accepted their value.

The last time I actually had to argue for unit tests was in defense contracting and not for the team I was working on. Some idiot at a lunch-and-learn community thing tried to claim there was no short term gain from them and we had defined short term in months. He could not believe that unit tests can help the developer writing them and the help the team the very next sprint.

I hope he learned better or got forced out of tech.
A job description might say C++ at the top but, it will be followed with a page of other requirements and weeks of interviews. They won't hire you unless you are already doing everything.
>As soon as you possibly can, start working on something you 100% agree with.

Man, that point resonates with me. I quit a while back due to severe burnout (actually, I think now, boreout) and have been struggling to get enthused about anything. I think what you said here is the core of why I might be done with tech as a profession entirely - I'm almost completely soured with the impact and direction of it as a whole.

So then the question becomes well, what do I agree with and want to do? That's a hard one. This is the only career path I've been on and even if I do find something else, starting off at 40 with no skill base is... oof.
A lot of Linux people have the impression that LibreSSL is largely incompatible with OpenSSL (not true), that the ABI breaks every six months (not true), or that it requires heavy patching of downstream software work to maintain (not true anymore).

Here's a recent presentation about LibreSSL and some of those points: https://www.youtube.com/watch?v=bF1d_aCSzS0

Years ago there was also a big article from Alpine, one of the distros that tried to switch to it and had to switch back. The now-outdated article seems to be the main citation for those opposed to even giving LibreSSL a chance now. In fact Alpine is reconsidering a switch back from OpenSSL after the 3.x branch was shown to be such a disaster.

One of the LibreSSL developers summarized this recent OpenSSL issue in a commit message worth reading: https://marc.info/?l=openbsd-ports-cvs&m=166731803502387&w=2
My guess is it's the same reasons that drive people towards gaming consoles in the first place, mostly convenience.
A refreshingly pragmatic position for an academic. Where did you get that quote?
> I don't understand the market for a device like this at this cost.

I am a software engineer and OSS enthusiast, I operate servers and my home automation system, but I gave up on PC gaming years ago. After a long day of fighting distributed systems, I want my gaming rig to just work. That's why I bought the first PSVR: because Sony offers me a system where I don't have to fiddle with drivers and windows updates.

Price is too steep indeed, but it will go down as the production ramps up. PSVR launched at 400€ in 2016, and I bought it at 200€ two years after that.
> But there are also private, non-governmental vendors that verify your physical ids and create verified credentials for you. In that case, the private DI vendor is the issuer of the verified credentials.

But who's going to trust those vendors? This is the job of the government IMO, one of the few things you just can't rely on the private sector for. I definitely don't want my birth certificate credential tied to, say, Google :D the Government cannot , for example, remove my credentials because I said something polemic, while Google (and infamously Twitter) most definitely can and seem quite happy to do if they can.
Yeah same, I’m an EE camping out in software because of the pay. It’s also just easier work. I would much rather be intellectually challenged coding firmware or embedded work. I didn’t go to school to build web widgets. It’s just EE pays so badly you can’t make the bills. I was getting offered numbers that wouldn’t have afforded my own studio apartment to rent. For EE work. It’s insulting.
Genuinely curious why anyone would choose Google Fi over a way cheaper prepaid plan that's almost half the monthly cost for roughly the same experience. Also Google support is truly terrible.
Too much variability in the home networks that people have are likely one of the reasons
They've already been doing this, just switched back to T-Mobile recently and it was $35/line for activation, and then afterwards we had an issue with the unlocked Verizon S22 Ultra because Verizon's firmware on the device was (intentionally?) broken, so we "upgraded" that line to purchase a new device and it required a manager to waive the $35 upgrade fee for the line.

That said, I'll take it, I was only on Verizon for 6 months and had nothing but issues, especially issues that just straight out shouldn't happen (phone got stuck thinking it was in Italy after our summer vacation after we returned to the US). I was a happy Verizon customer more than a decade ago and thought going back would be a good plan, but it turned out to be a nightmare that ended up costing me over $1000 for no reason, and the Verizon policies and customer service are horrible.

T-Mobile is the only US based carrier that has reasonable international roaming for data and non-stupid policies. If they go evil after merging with Sprint (Sprint is horrid), then we'll have nobody left, just like most other industries in the US that have become multi-headed monopolies.
You are right that some problems remain.

The Rust compiler team is working on speeding up build times as we speak. Give it some time. If a language was perfect in other respects (e.g. free of memory leaks), I won't mind waiting a little longer for my builds, but I know this bothers many. In any case, it's being looked into.

The complexity argument I agree. Rust won't be the last language for that reason. Already it influences languages like Zig and Jakt, who aspire to be simpler and still suitable for systems programming.

I disagree re: ugly syntax, but that's a matter of taste.
> It seems weird to call the process which is literally essential to using a device on the network "essentially nothing"

It should all be automated and if it's not, their CTO should be fired.

Activating phones is literally step one to get customers on a 24 month cycle of predictable, recurring revenue. If you can't make that seamless and low friction, then you should not even be in the business of selling cellular plans.
>...praying it lands in Siberia and not NYC.

or vice versa.
> You see a hundred blog posts of "why you should experiment with your pricing", but actually doing that is often such a pain that nobody ends up doing that (and admittedly the reason why I would have shied away from such projects in the past).

Yes, exactly. Especially when those same blog posts tell you to plan to basically have your whole team focus on it for 3 months, as if you have nothing else to do!

> - What are your plans like regarding the integration of entitlement checking in the service and SDK? As far as I can tell, that's still a missing piece? I really love how oso[0] has managed to separate the authorization checking from the authorization definition via their DSL and SDKs. Ever since I saw that, I was wondering if a very similar system could work for entitlement checking.

The SDK does expose a `tier.limit(org, feature)` method[1]. This is reasonably fast, but if it's uncached, it is an API call to Stripe, so it can be beneficial to have that drive a proper feature-flagging system like Launch Darkly, or whatever else you use to manage authorization and feature availability.

> - I think where your system could provide a lot of benefit would be in help tracking usage metrics that can be harder to calculate (and with that more of a pain to use). It's already nice not having to implement a simpler "number of action N taken the last billing period" metric. However something like a "N number of active users last billing period", where you now would also have to keep track of which users you have already seen before to prevent double-counting them becomes increasingly annoying to implement.

For seats you could use an `"aggregate": "perpetual"` setting on the feature. See: https://www.tier.run/docs/recipes/#simple-per-seat-pricing (that page also has some other examples that might be helpful.) With that, you'd just report the increase or decrease every time the seat count changes, and the counter would never be reset. (There's a few other ways to approach it, but that's what I'd do, as it's probably the simplest.)

You're right, though, if you want to charge based on active users, then it gets a bit more tricky, because you do have to avoid double-counting. And the precise definition of "active" becomes really important. I'd probably approach it by putting a "lastSeen" timestamp on each user account, and then periodically calling `tier.report(org, "feature:activeusers", numberActiveSinceFirstOfMonth, Date.now(), true)` to clobber any previous value. (`clobber` is not the default, since usually you want Tier to count it for you.) I'll add an "active users" example to that recipes page.

[1]: https://www.npmjs.com/package/tier#user-content-limitsorg
I hadn't considered that. Hope it works out for you. That was a brief moment of trauma reading your story.
It’s almost certainly output and not manufacturing time.
I'm surprised that we haven't seen even a modicum of uproar from a contingent of the currently verified that selling their status for $8 a pop dilutes their prestige. Instead this is like the eight dollar version of "I Am Rich"[1].

1. https://www.latimes.com/archives/blogs/technology-blog/story...
Musk's goal is that "the factory is the product" [0]. He's always focused on production efficiencies. This was brought up in the Tesla bot presentation also where they're trying to reduce the number of unique parts.

[0]: https://thedriven.io/2021/01/12/the-factory-is-the-product-m...
Fellow Deutsche Bank customer??
Very cool, thanks for this
A love letter to React from Phoenix
> It doesn't need to be mainstream, nor do I want to be mainstream.

Who t f are you? You seem the narcissistic here.
Don't know about easy to imitate, but Herzog's voice is quite distinct indeed. A couple years ago I was watching a Tom Cruise movie ("Jack Reacher") on German TV and very surprised to hear Herzog as dubbing voice for a supporting role.
Cartels are illegal in the United States, right?
I would have thought output; the machining, heat treatment, etc. is demanding and involves many tools. Assembly is a whole other phase.
Problem is, for me at least, Google is useless for predictions or recommendations. Search is still better than DDG, but way worse than peak Google.

Their recommendations are all over the place despite the fact that I have been logged in permanently in some form or another since GMail where still invite only.

No one else except my wife and my parents know more about me (and to be perfectly clear they know different subsets of me) but yet Google still insist on showing me the most irrelevant and annoying ads and suggest I call people at work in the middle of the night etc etc.
This may be an attempt to appease their store franchisees by eliminating the cost advantage of avoiding the stores. Why compete against your own franchisees?
I hope so. I hope it won't be the case where it's enforced that people have the ability to send money instantly but the cost isn't capped.
This whole comment reads as a series of rationalizations. I like Rust and write software with it, but I also understand that Rust has some big problems, that are either a long way from being fixed, or will never be fixed.

> The long build times are a product of the type safety mechanisms built in.

The long builds times are a product of the crate culture. Like JavaScript, many people are happy to pull in crates that are tiny to avoid having to write anything themself. So you end up with many packages pulling in over 100 crates.
> praying it lands in Siberia and not NYC

The Siberian Tunguska event was thought to be caused by a 20m diameter object hitting the earth. This is talking about a 900m diameter object which likely has 100,000x the mass of the object that hit Tunguska.

EDIT (per comments below):

400,000x the Chelyabinsk object

27,000x the Tunguska object
The solution to this complete transparency for all, but that is also a pipe dream.
Their actions aren't "too extreme" they're too _arbitrary_. Attempting to vandalize paintings isn't helping anything. From what I've seen the media attention has been on how immature environmentalists are, not anything related to required environmental changes.

There is already widespread awareness that something needs to change and these tantrums are just noise drowning out any useful signal.
I switched my ex off my Verizon plan to Visible. It cut costs by 60+% for service they haven't seen a difference with.

They lost the ability to go into a store for support, lost phone support, and get deprioritized but they use it for personal use and don't care.

I use my phone to run a business. I will spend the premium to have the best service I can afford to run my company. I pay for the top plan on Verizon as a result.

Choice is good. An MVNO is not for everyone but it is a much lower cost option for those who want the downsides.
Will nationalism end the golden age of global AI collaboration?
Rust is already hard and complex enough. I worry that Rust++ would be a monster like Kraken that would chew a young programmer me at one end and spew out an old and confused person who is struggling to understand how all his youthful life passed by without even realizing that it did.
Hospitals and the medical profession have a lot of work, and for efficiency they stack the work up. A rule of thumb whenever dealing with a hospital is that everything will be massively later than you expect. It's a good idea to set your expectations ahead of time so that a bit of a wait does not take you by surprise. For a hospital procedure, half an hour late is pretty much right on time.

Congrats on the baby!
I've been on Mint for over a year and have been really happy with it as well. It's saved me thousands compared to T-Mobile, and now that my wife and I work from home full time we really don't need much data at all. We each have 4GB/month, and most of the time I barely use 2GB.
I've contributed to OpenSSL in the past, but not regularly.

Heartbleed was partially because they hadn't fully adopted techniques like fuzzing in regular use, so when researchers started fuzzing everything, out popped heartbleed. Now OpenSSL does fuzzing on (every PR, IIRC?) The author is a bit unfair in calling the project out as if they don't do it.

There still aren't a lot of developers on it relative to the complexity of the project though. Frankly there are large parts of the codebase that are pretty intimidating to touch, like the X.509 stuff implicated here.
Why do many people (including myself) like what Elon Musk's doing, and why do we disregard all the hit pieces and smears targeting Musk across social media (very prevalent on Reddit, etc.)?

It's because SpaceX and Tesla are the clear leaders in opposing the de-industrialization trend in the hyper-financialized American economy. It's so incredibly stupid and short-sighted to move manufacturing and the associated technological R&D outside the United States, as it results in the loss of critically important technological skills. Follow that route and you end up with financial institutions desperately trying to retain control of technology via intellectual property lawsuits targeting countries with their factories in China, which as history has shown, will alway be a losing battle.

Rolling back the financialization of the American economy, and re-introducing industrial activities at scale, is the only way the country will avoid devolving into a dystopian Third World system of wealthy enclaves with large capital holdings (protected by private security armies) surrounded by miles and miles of festering slums.
The scope of Science has been set by private capital, but the Chinese lockdown is very clearly a scientific endeavor. Might as well compare vaccines vs. lockdown as two scientifically-informed tactics, although the two aren't mutually exclusive, as in the case of China.
that should raise the salary on the market, not lower it
Sounds like you might love doing meaningful work.
>> Rarely does a life leave time or energy for child-rearing, a paid job and a fulfilling avocation.

> I could not imagine living a world where this becomes the norm. The norm should be "It's rare for a person to have a shitty job, a mortgage, student debt to pay off and no financial possibility to have children until they are 65".

This is the world you’re living in right now, it just sounds like you’re one of the lucky ones who doesn’t see it. For every worker who can sit home and code, there are at least hundreds of people doing menial jobs like harvesting crops, packing shipments, drilling for oil, fixing streets, etc. Most would probably describe those as “shitty jobs”, and sadly those jobs barely pay the rent.
> Back in the day, the AI for opponents was often fairly stupid. Rather than spreading out intelligently to prevent an opponent from reaching the goal line, they would just sprint towards your current location at all times. So if you run in a bit of a loop from where it makes sense for you to actually go, you can get the opponents to chase you in a long line. Not hard to dodge them almost indefinitely in this case, allowing you to take an arbitrary amount of time off the clock. Real players won't behave like this.

Imagine seeing someone pull off THAT tactic in a real game!
I get it till I don't.

What I get: In-store activations and upgrades are time consuming in many cases. I think every time I've gone to a TMO store to upgrade a phone for myself or a family member, at least one other person/group is there doing an activation that for reasons I cannot fathom takes at least from when I arrive at the store, wait 30-45 minutes, finally get handled, get activated... and that other person is -still- going. It's a huge time-sink.

What I don't get: charging the full price for online activation, when you're not involving nearly as many employees. It will potentially backfire, I know if I'm paying 35$ whether I do it myself or have someone else do it for me, the value-prop changes and I might just go in and further load their stores.
> It’s a pain to start learning C++, and even after you do, older devs will roast the hell out of your code because your book/tutorials of choice forgot to mention a crucial

Preach it!
I don't understand why you think they should have picked a different name.

An overwatch [0] is someone who has a better vantage point and can make tactical recommendations because of that privileged position. The point of the tool described in the paper is that it can see everything you do and everywhere you go within the code, so it can make better code edit recommendations. It's an apt name and makes perfect sense.

The fact that a video game shares the name is completely unimportant. This is an academic paper, which means people are generally not going to be using the tool itself ever (and it's not meant to be used like that). The only people who are going to be searching for it are people who've read the paper. A common purpose of papers like this is to provide a proof-of-concept so that a more fully featured version of the tool can be incorporated into proprietary software. As a consequence, the authors do not need to worry about what might be called the "marketability" of the tool, especially not in terms of name selection.

[0] https://en.wikipedia.org/wiki/Overwatch_(military_tactic)
I guess it depends on the subject. E.g. no cameramen will take a good photo of flying birds with a shitty camera, but sure enough in good lighting conditions static scenes can be remarkably good even with worse hardware.
> a way cheaper prepaid plan that's almost half the monthly cost for roughly the same experience.

Which prepaids? The last time I compared Fi to my prepaid plan they were roughly the same cost.
Sound Burger and the Clones
Isn't that nuts? It basically comes down to, if you're further from management, you're not valued.

Oh, you can change the color of the button on my website? 200k/year!

You eke out maximum performance from poorly documented devices and apis using obscure toolchains and custom built linux kernels to run on small chips that are the backbone of our business? 75k/year!
Google Fi is great if you never leave the US. If you spend more than 30 days outside the US, you can be penalized due to roaming, even though they have a similar offer/capability to T-Mobile for data roaming. On top of that, it's tied to your Google account, which comes with all the drama that means like the recent story about Google arbitrarily shutting everything off (including Google Fi) for the guy who took photos for his doctor.
I’ve been in both web and embedded for the last 20 years, and to me web dev “done right” is just as much if not more complicated than embedded, and very similar. In both cases, you have a distributed systems (everything action you take, system wise, is asynchronous, and very uncertain). Debugging is a pain in both cases, because you have only limited access to the system under test (especially in the field), and things like minification / optimizing compilers make it hard to necessarily track bugs.

Embedded has the advantage that you can usually trust your peripherals more (they’re not a user that randomly presses CTRL-R), there is less framework and thirdparty stuff in your way, and the timing constraints are usually better understood. Webdev also suffers from a ton of UX and UI (animations, wizards, complicated workflows, error handling that needs to be error handled that needs to be error handled), which often results in very complex state machines.

In both cases, observability is key, especially for debugging purposes. I use the same patterns in both cases: a lot of state machines and event driven design, because I get “debugging” for free (I just need to log state + events and I can reproduce any scenario).

The big advantage of web, and one that I always have to adjust to when I come back from a period of time in embedded, is that you can YOLO a lot. YOLO to prod, you can always easily revert. YOLO the UI, because you can trust the user to refresh their page or workaround it (your hardware peripheral won’t). YOLO everything because you’ll never really brick stuff. YOLO timing because you usually don’t have hard or even squishy-hard realtime requirements. YOLO behaviour because you can have realtime feedback on how your system is doing, and pushing a new version is only minutes away.

But “web dev” done right, and I really like having something fast, robust, repeatable and observable, is quite the challenge too.
Someone did write up a paper for this, but it isn’t happening; I can’t remember if it was rejected formally or what exactly happened, all I remember is it’s not happening.