Master_Odin

Looking through the site, the developer's "Show HN" and ProductHunt posts mention that the app was "open-source", but I could not for the love of me find any links on the site to the source. Had to turn to google to find it: https://github.com/DevUtilsApp/DevUtils-app.

Of course, given that the license is the super restrictive CC-BY-NC-ND 4.0, so I guess makes sense to not bother advertising it given the very limited freedoms that are available.

Actually, it looks like it is paid source available: https://github.com/DevUtilsApp/DevUtils-app

But I could not find anywhere on the site that linked to this repo.

I think parent might have meant "offline". Definitely doesn't look like devutils or devbox are open source.

It's probably a simple bot that's hooked up to a GH app. Then just some custom code to react to specific types of events. Depending on what you need done, you'd possibly be able to replicate a lot of functionality within a GH action.

Are you equally appalled that so much other government paperwork goes through the mail? If we can't trust voting by mail, then we certainly can't trust mailing passports, visas, IRS forms, car records, etc.

It's weird to me to single out voting as the one thing that can't be trusted to the postal service, especially when there's things like voting lock boxes that are kept under camera you could put your vote in.

One thing that doesn't look possible from the spec is supporting recipes with multiple discrete parts. An immediate example for me would be I made a fish dish that had an optional salsa to put on top. I substituted the salsa for something else, so given a recipe, it would be nice to see "here are ingredients for the fish, here are the ingredients for salsa", and that they don't go into a unified singular count of ingredients.

As someone who has started learning Ruby to contribute to one of my companies' repos and the amount of "magic" in Rails has been a big stumbling block for me compared to any other language I've worked in lately (JS/TS, PHP, Python).

And after whoever started the project gets their promotion, the product will be killed off and Google will chase another shiny thing. How much does anyone trust totally new Google things these days?

This has been the big slowdown for my org as a number of packages we rely on in docker on debian do not yet have an arm64 version, so have to emulate x86 and take the huge performance hit.

All of these projects joined the .NET Foundation though. Was there any contract they signed or agreed to as part of joining the foundation? What were the terms the orgs agreed to?

I think we can all agree how the foundation handled this was really bad, but if you don't like having the risk of a foundation unilaterally doing stuff, don't join it a foundation?

How is building proprietary plugins for the editor they themselves created and maintain at all part of EEE? Unless it's someway to extinguish LSP, which they also created?

This just adds burden to programming language and library authors. Sure I could almost certainly support Python 2.7 and Python < 3.6 in all my libraries, but it introduces more code and shims I've got to maintain. Given I'm not being paid for this work and do it for fun, there's no compelling reason to support the small subset of users that cannot or will not update.

I imagine variations of the above apply to nokogiri and some amount of Ruby core developers.

But this can happen anyway during the "regular" support window. I had this happen to me ol years back and it made booting the phone go from a few seconds to minutes as it had to do something with each installed app. This eventually got me to put a custom ROM just so I could stop having this bug, all because the manufacturer (Samsung) stopped caring about it.

While composer does have this limitation in that packages are published by making new tags within the repo, frameworks like symfony and cakephp have workarounds where they have one monorepo where all packages are worked on, and then automation to push changes to read only repos of each component. So there's https://github.com/symfony/symfony pushing to https://github.com/symfony/event-dispatcher which gets published to packagist.

China is very competitive in the moba genre, like League of Legends and DOTA2.

The mysqli extension in PHP is fine to use and has advantages over PDO if you only ever plan to interface with MySQL. Now, if it was recommending the mysql extension, that would be bad as that's been deprecated and replaced by mysqli for a very long time.

The HOA can not restrict purchase sure, but can specifically target PoC for "violations" while ignoring the white households who are committing violations. This has the effect of working to force these folks out and maintaining the racial status quo of the HOA.

In the 70s (I think) and before, HOA were definitely active gatekeepers though against PoC, and then after that with new laws passed, moved to these more "subtle" methods.

MS products are going to stop working with IE 11 come August, seems like it's time as an industry to force its retirement on any holdout managers.

Do elixir libraries just never deprecate stuff? Or just that their package managers never alert you about vulnerabilities so you can pretend like they don't exist and so never upgrade?

Except more harsh policing is not the answer to this, especially the opioid crisis. If you want to see less crime and drugs, you improve the conditions that lead people to crime and drugs and then increased social work when people do run afoul.

The current police system in the US does not do that, and the prison system is purely set up to incarcerate folks and then ensure they will fail when they get out so that they end up going back in because gotta grease the wheels of prison capitalism.

The pull_request_target event however allows for read/write access to the base repo and access to all of its secrets. It's not the event type you'd want to use whenever dealing with code that's incoming in a PR.

See the big warning at https://docs.github.com/en/actions/reference/events-that-tri....

Can the python packaging story get much worse? It's a huge blemish and way too much fragmentation and after market solutions, and of course the mental overhead of virtualenvs or else you clobber your environment.

One thing I keep hoping will get advanced in is PEP-582 to incorporate a local __pymodules__ folder since it would be nice if getting a python project up and running was as easy as node or php.

These will go away in v5 (if a v5 is ever released) and is not recommended if using a bundler as it'll end up wasting space rather than saving as it'll include duplicate code that each individual function could share.

https://lodash.com/per-method-packages

Similar thing happened to me with Itau in Brazil in that their website was barely functional (with the last month I was a customer I couldn't even login in) and had to do everything over the cellphone app. Super annoying as I wasn't a native speaker of the language and desperately wanted to use my computer for ease of use with translation software.

The AsciiDoc example is an interesting one as I've not seen really any discussion about "whitespace" as offensive and cannot really find anything. Add onto the fact that stuff like wikipedia also still refers to it as whitespace as so it does seem like they're going to define their own term for AsciiDoc that'll be at odds with broader community and just begs for newbie confusion.

At least in this instance, the racial biases of facial recognition will not be a problem for the overwhelming white mob.

"Begin rollout of feature <foo>" "We are rolling out <foo> in <timeframe> to ensure <x> about <y>, and rollback if <z>. You will notice you have <foo> when <bar>."

If you don't put anything about new features, don't be surprised when users don't use them (because why would they know) or complain what something "breaks" (or just changes on their workflow) because your changelog communicates nothing.

A lot of these pieces on "ethical AI" just seems like theater to me. I'm sure if you ask the authors of the modern techniques of facial recognition, they'd tell you all about the wonderful and great things you can accomplish with it. And yet we also have state actors using it for great harm, and this is true of a lot of foundational AI work that then powers AI solutions to problems.

Maybe this kind of "push" from conferences will help power a change, but the given the replication crisis (which the author mentions) has been well known for a long time and nothing has really happened on that front, I wouldn't hold my breath.

Reproducibility would be a problem in scientific circles regardless of language. Researchers are negatively incentivized on reproducibility to avoid scoping and the like.

C# and F# are great examples of how MS is willing to allow people out of their ecosystem to use them with all their efforts with .NET Core and having it run places other than Windows.

npm is trivial to replace with yarn and a custom registry.