Post date: Feb 03, 2018 3:46:46 AM
Here is an aside, which is not SQL-related, but definitely baka, I tried to get bridge.net working in visual studio code. Completely lost cause, representing about 40 hours of lost time, mostly installing software. Cross-platform development it certainly is not.
The idea sounds neat. Write C# code, get JS. JS is a slopfest but this forces cleaner code, and the compiler catches errors that otherwise aren't caught until runtime. I love the idea. But it's a no go if you're not on Windows.
The new CLI doesn't run in wine with mono
Doesn't run in wine with dotnet40 or dotnet45
The old demo project, which they removed all references to on the download page, is almost impossible to find with Google.
I learned some things about Google when trying to find the files, such as ...
Without allintext:, google now returns results completely unrelated to what you're searching for; search quality took a sudden nosedive starting this morning
With allintext: the results are slightly better, but google thinks you're a bot if you use it
The demo project won't build with mono xbuild (this is actually deprecated)
The demo project won't build with mono msbuild
VSCode doesn't recognize packages installed with nuget
VSCode doesn't put red squigglies under namespaces that don't exist or objects in a namespace it can't read. Regular visual studio tells me when i'm writing bad code, for which I am grateful.
In the end, wine, mono, vscode, and bridge.net all fall down. VSCode comes out the best because it looks nice. It's amazing what can be done in a browser (view the developer tools ... it's all a page in Chromium). But even that, without the ability to keep me from making dumb errors, it's really not much better than Notepad++. Looks like I'm stuck with the full VStudio ... which is not at all cross-platform. On this PC, it takes around 5 minutes to start up, frequently freezes up for short periods of time, and only stays usable for about 30 minutes before a reboot is needed. I was really hoping for something Linux-native.
UPDATE: I think Intel has screwed me, because now Visual Studio won't run (well, it will run ... it just takes 2 hours to start up) in virtualized Windows. The big changes are the patches for the Meltdown vulnerability in Intel CPUs. Previously, it was practically unbearable, but I was able to get quite a clean and organized Javascript framework built, along with a simple proof of concept for my application. And now I can't get any more done on it unless I start over and do it in pure JS.