- I dislike javascript for large projects because even the best tooling is lacking, and the exploding dependency count.
- I love C#, but WPF renders worse than Electron (and Windows only).
- WinForms - mothballed.
- VB6/Delphi are EOL.
- UWP - Very lacking, will probably be abandoned.
- Java - I have no experience.
It will be a case of Flutter sucking less than the current options. Dart is actually a nice language, especially considering the runtime size - there's no framework overhead/bloat.
I imagine it to be Electron, but with a decent set of widgets and without the overhead.
Edit - to answer the main question:
Personally, I wouldn't develop anything more than a throw-away or personal project right now, but it's worth keeping an eye on it.
It would be nice to have a cross-device framework.
> because they are prepared to do work locals are not, at a price that locals will not consider.
Fortunately, those locals are able to purchase their produce at a lower price, with the benefits they claim which is being paid for by the migrant's taxes.
At a butt-in-seat job, I'd turn up on time and leave on time - and that's the end of it. If during those hours I happen to be in an unproductive mindset (eg, unable to concentrate) then so be it. I'm paid for my time. If I happen to be in a productive mood after hours, their loss.
Now that I'm working remotely, if I'm feeling unproductive then I will stop work and do something else (shopping/walk/etc.) and resume when I'm more productive.
I also don't mind being contacted out of hours (I'll decide if I'm busy or not) - they're flexible with me, so I'm flexible with them.
They'll get the same number of clock-hours from me, but with more work output.
Yes, this is a great point. If I "felt stupid" when I was in the office, that was fine. I would chat with colleagues or just look out the window. On the other hand, if the same thing happens at home then I feel guilty about it, "stop the clock" and then resume later.
I would discourage development for Windows but not necessarily on Windows. I develop on Windows and deploy to Linux all of the time. I also have started using the Linux subsystem for Windows.
I’ve been developing for and on Windows for over 20 years. The “Windows Tax” didn’t become a concern of mine until I started using cloud providers. The cost of Microsoft’s licenses was someone else’s problem.
But, when every resource you use is tagged and it’s very clear how much you’re spending on an implementation, the double hit of Windows becomes real. First you pay more for Windows VMs than the same size Linux VMs and then you need more resources.
I can do a lot with a 256Mb-512Mb RAM Linux VM. I at least need 4GB of RAM for Windows and that’s stretching it.
On the other hand, I still love .Net Core but it’s not getting the uptake that Node is or even Java - yes that makes me sad.
It's a philosophical difference. NT doesn't do overcommit. In theory overcommit is dangerous (and if you decide that matters you can tell Linux not to do it) but in practice it's usually a huge RAM saving.
If your apparent virtual size is 2.6GB but there's actually only 240MB of resident memory, Linux will run on 256MB of RAM. NT requires enough RAM for the entire 2.6GB plus overheads.
This is especially frustrating if you have orchestration services that would have recovered from the unlikely event of OOM since avoiding OOM is literally the only reason for NT's choice.
Personally, I've run small LAMP stacks on VPS's with 256 MB RAM and without major issues. Running a web server on a Windows VPS usually requires more than that (albeit not 8 time as much.
A lot of families already have a Windows computer and not everyone can afford a spare computer to run Linux on, and some people's PCs can't run a full Linux in a VM either.
Windows has a lot of ways to develop for Linux/Unix now. It sure isn't FOSS, but let's not discourage a promising way to get more people into software, even if it's on Windows.
The "installing" part is the problem here.
I installed Manjaro XFCE in my parents' old PCs, and they're now enjoying it. They never did it because they didn't know how to and didn't want to destroy their already working, but slow PC.
Teach that, and I'm pretty sure everyone would love the customizability that the world of Linux provides.
Do you have any specific points or you're just trying to be edgy?
Hint- no circular arguments allowed. For example- UNIX line endings are '\n' so they are better so look UNIX is better. I mention this because I've heard this from my friends none of whom have ever programmed a raw terminal.
$ bc
bc 1.06.95
Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
^C
(interrupt) Exiting bc.
I don't use Chrome/Firefox but this surprises me, as well. The presence of a private browser window (anywhere) will prevent it from deleting cookies when you close this private browser window? That seems completely counterintuitive to me. When else, in any application, does the mere existence of an open, empty window completely change the behavior of a different window?
Safari's private tabs are each completely independent.
