webprofusion

Just use Caddy https://caddyserver.com/

Java 8, as in from 2014?

The most sustainable thing we could do for web capable devices is to make right to repair mandatory and include in that driver specifications required for custom software/firmware. e.g. an old iPad is now obsolete, but it may work fine it just can't connect to modern TLS and doesn't trust new root CA certs.

If it was possible to updated old devices with any custom OS, many devices would continue to work instead of being disposed of.

Oh you mean Python library APIs. I totally thought this was going to be a generic article about APIs delivered over http, the first thing I'd think of when someone says API.

Cool but the fonts are all messed up.

I don't think this is the right solution to the problem, but it looks great.

The single biggest problem we have is human hubris. We assume if we create a super intelligence (or more likely, many millions of them) that they'll perpetually have an interest in serving us.

Like it, I think it's cool. Base 64 decoder/encoder would be cool, as would a PEM decoder.

Have added DawVert to https://github.com/webprofusion/OpenAudio

The assumption here is that we care about plugin state. I have audio projects with minimal plugins and the first job is converting the track structures (including cropped/transformed wavs), plugins are replaceable in many cases but it perhaps depends on the genre and composition style you are targeting.

Great idea! Would love something that converted old Cubase .all and .cpr projects to other formats (very hard to reverse engineer though).

Lol, try upgrading old MongoDB stuff.

Database engines (every single one) are notorious for incompatibilities between major versions, upgrading mission critical stuff means updating and re-testing entire applications, which in some cases can be a multi-million dollar process, before going into production.

Even if you deeply know/think that there's no problem upgrading, if something does fail in production after an upgrade and it's mission critical..

This is largely a solved problem. On Windows https://certifytheweb.com has provided automated certificate management for the best part of a decade and we're now branching out into large scale cross-platform tools, for those interested.

I was surprised by a customer yesterday who was looking to migrate thousands of manually renewed 1 year certs, I had no idea people were still using 1 yr certs to such a broad degree.

Sorry, why is this on hackernews?

Next you'll be telling us to use spaces instead of tab.

Definitely had to read that subject line twice.

This is (potential) an advantage of small teams and individual developers. In more formal teams developers are often handed a UI and that's what they have to build, no variation permitted.

However, not every developer will craft a great UI just given time, I've seen some truly inspired monstrosities.

This as good until I got to E! The linked page is really the A-D of product psychology.

I'd second that. If someone is circumventing your licensing checks then they're not a customer, but on the plus side they're effectively the same as a free plan user (with zero support) and maybe in their next job they'll recommend using your tool and getting a real license, or maybe they'll get tired of hacking each update and just buy a license.

I can see the idea that the OP is suggesting but decades of keygens and hacking have taught us that if someone really wants to use your software without paying, then they will.

I've seen people craft elaborate ways around my own software licensing check when the actual "hack" is jaw droppingly simple (and is all on github), the point is that the people you need to concern yourself with are the people who will pay for a license.

I've built a few open source things in the past, a couple of which got popular. One was an open data project and it's just stayed the same (free API etc). Community look after it mostly.

Another was what became Certify The Web, which is now the most popular UI for automated certificate management on Windows and is most definitely now a commercial product (but 90% of users use the free version). I originally had a donate button and did get a couple of donations, maybe 4 or 5.

It was getting thousands of downloads per week and the company I was working for went into administration, so on the same day I added a Paypal button to the website for people to buy a license key and got my first sale later that evening. It's now had around 10K customers over 7 years and they renew their license key each year. Some people/companies do indeed want support and updates (I offer email support only, or there is a community forum). Nowadays most purchase via Stripe,

Now do the same using Blazor Server (C#). For convenience use https://www.fluentui-blazor.net/ or https://mudblazor.com/ for your UI components.

It has it's compromises but it's great for just building stuff, with UI updates streamed to the client, no JS (or as much as you want), no extra API building just for the sake of your SPA. Note that I'm not talking about Blazor WASM.

If you're interested in working as a developer for corporations outside of the SF bubble (e.g. the other 80% that use Windows instead of macOS) it's worth checking out, especially for internal corporate stuff.

Agree it's complex, and when attempting to solve a particular problem you end up with yet another license every time.

What businesses in particular want is a "Yes, you can read the code and yes you help if you want to, but you can't use the code to make your own product" source-available license (because they have devs to pay, and being able to keep doing that is the first thing they need to protect).

I think such licenses do sort of exist but they're fragmented.

The root of this particular argument seems to the definition of Open Source meaning unconstrained use of source code, instead of source-available.

As battery innovations go, this one seems relatively trivial to implement? The bigger problem is probably shipping battery packs that are sitting fully charged for a long time before the customer gets them, depending on the chemistry.

Absolutely get rid of that signup page, not going to try it out if I have to sign up, soz.

Love all the features of this app, the chromatone part is just an element but the theory and scales stuff is nice.

Just run the model locally?

Err, you guys know that about 80% of desktops are Windows right? There's a bit of a myth that developers are all using macOS but in practice that's not really the case.

Lol, checking out the readme. Dunking on stuff isn't what makes you an opinionated framework.

Keep in mind that if you are publishing reviews (or regurgitating them) you should also have some insurance in place for product liability. Other businesses get a bit annoyed if someone says bad stuff about them and in the case of review that's stuff you didn't write, but are still publishing.

If you can solve this problem then you have solved entrepreneurship. Really you need to start to promote the project (as you have done here) and start to gather traffic to your site, while it has a minimal feature set. If you over-engineer and over-develop to get it "perfect" you'll just waste time that could be spent on another idea. Launch the most basic version and get links going to it from blogs, facebook groups (etc) and other established websites.

Even if you publish the best and most useful app in the universe, if nobody knows it exists then does it really exist?