Is that like a Palm Pilot? Seems like 300 years ago.
673 karma · joined May 31, 2017
Years before that the free certificate authority Let's Encrypt was established (there are now several more), so for most people using https with your website is just configuration, not an extra cost. On top of that some http protocol versions are now https only.
From helpdesk you can then move into specializing in whatever you are interested in. Software development is a competitive field and is constantly in technological flux, but there is stable work behind the scenes if you don't chase the latest trends too much. If you want to do it I would suggest looking for a PHP job rather than an AI job. Freelancing is very piecemeal work and hand-to-mouth, which is the opposite of what you currently need.
For instance a guitarist will have a track they wish they had vocals for(and lyrics) for and if they could pay for that they would.
Literally if you could highlight a tune section in your DAW, prompt it, and vocals + lyrics were generated, possibly different version or harmonies for existing parts etc. Musicians already pay for plugins but the singing ones are awful to use so far.
https://learn.microsoft.com/en-us/dotnet/fsharp/whats-new/fs...
Dotnet has compilers for C#, VB and F# and they can all share the same frameworks and libraries. C# is the most popular.
If we all take the easiest path it will also be the slippery slope to the bottom.
A bit of back and forth discourse is fine and expected, but if you keep pushing someone who has their own legal dept they're eventually going to wander over to the coffee machine and have a chat about it with them, then they're going to take a look and it becomes their problem.
So the number one rule would be don't even breath the word "legal" unless you want to invoke them. This particular response is just a letter telling them to back off and it's why you have a legal dept, so they can argue with each other. This one has just found it's way into the open.
There is a understandable perspective that says CAs shouldn't be burdened with legal risk in their discussions, but that's contrary to the fact these guys are commercial entities protecting their interests, so you don't get it both ways unless all your CAs are non-commercial, and even then that would only extend so far.
Could maybe have a simpler UI by default with an option for advanced as most people would be consumers, not creators.
Could be fun to browse other peoples work if ranked by current popularity.
The app itself (Midi editor with piano roll UI) looks great but is instantly made much less relevant if you just install Reaper (and actual DAW, free to try, available at the time all this was developed).
Cool thing, but the moral of the story is: release that toy thing you spent a few weeks on, it's as ready as it ever will be and maybe it'll grow with it's user base.
Experienced devs can do so in a first pass to flesh out an idea before letting the team get involved, but thereafter the design immediately becomes rigid. Inexperienced devs can wing it to learn in an exploratory way, but their work is unlikely to be re-purposable.
Around 2013 I built a guitar tab synced to youtube video proof of concept thing and promptly let it rot, should have done more with it!
As we've recently established, we apparently do like to watch the world burn and maybe that's just where we're at for now, like a pressure release valve.
Yes Linux will definitely be one of the operating systems used on these new PCs, and they may even run Linux more often that not but if we assume computers largely exist for business to happen and money to be made, Windows is never that far away.
Safari trails chrome because Google didn't like Apple being in charge of the Webkit repo, which led to the Blink fork (the Chromium engine).
Firefox is still a great browser, but it has fallen back to square one on popularity.
From an anti-trust perspective Google should offer to fund their competitors directly instead of splitting the browser out, the eventual result should be revisions to web standards specs to ensure they are correct and detailed enough to be accurately implemented, which in turn makes new browsers easier to implement. Eventually if specs are close to 100% correct it should be reasonable to generate new browser engines from them. Currently that's not possible due to chasms of ambiguity and contradiction, and because browsers like chrome occasionally implement their own design of stuff just because they want to.