It has been a very good strategy so far. Stock is up 3x in a few months. Hopefully MicroStrategy can spin off the software part of the business and just buy bitcoin.
What unions have you seen/participated in? What countries are those located in? Could you imagine a union that does something that is not shared with those unions you've seen?
Being unlike other unions doesn't have to bad, could be great thing. Why not improve on top of the idea of unions and try to come up with something even better? Seems like an excellent idea, especially in these times of "disruption" of industries left and right.
You might get a Google indeed; some new vehicle that helps move society forward. But I suspect a very dangerous Theranos; except the union members will be left holdng the mess after it blows up .
From the definition of unions there isn't much overlap. Yes they want to protect Google Workers from harassment which is valuable but doesn't sound like they're fighting for improving wages, benefits, or working conditions.
https://en.wikipedia.org/wiki/Labor_unions_in_the_United_Sta...
Has anyone seen a big - multi year system done in FP? Lots of people love FP, it seems great for your own side project, but I'm not convinced it works in those typical big corporate systems where devs turn over every few years as the code base grows.
Technical debt can exist in any product and for a variety of reasons: inexperience, frequent employee churn, lack of leadership, frequent change of product direction, etc. Your comment implies that the technical debt is with Clojure the language or because of it. Beware of single-cause explanations of inherently complex problems.
I've designed and worked on systems with both OOP and functional-style code. Clojure is a tool that very much helps minimize technical debt. I think the minimal use of managed state in Clojure plays a crucial part.
Having done a good amount of looking through the Clojure language code itself, there's very little (if any) technical debt there.
I've worked in big F# projects in banking. It's absolutely superior to C# or Java in many ways. One notable drawback is "how much code can new hires write in their first month" which is not a metric I consider that important for big enough projects. The month or so needed to skill up a C# or Java programmer in F# is a drop in the bucket compared to the benefits it brought us.
Pitch (from Berlin) is using Clojure as well as Reagent with React. From what I saw it's quite a moderately sized app (not a gigantic one, but not a side-project sized either, in between that's what I mean).
Service Now has an incredibly clunky UI in terms of actually finding what you want, but at least in our JIRA Datacenter vs Service Now (it's under a service now domain, so I assume some sort of cloud setup) setups with several hundred thousand issues in each, Service Now is actually pretty fast in the sense of "You click an action and it does it's intended purpose", where JIRA falls down. It's slow only in the "You need 5 actions to get to the thing you want" sense.
I worked on a big distributed system with C# and windows servers. Was rock solid I miss it so much. I'm not drowning in Java/Spring/Linux app its such a horrible mess, security is the worst nightmare but even stuff like NFS is regularly breaks. Windows was great.
Well, things have a tendency to come full-circle again. Maybe with the cloud offerings, we'll realize that open-source isn't so great and go back to more proprietary offerings.
C# is basically the same thing from a VM perspective, an interpreted bytecoded high-level language, but tied to windows. You can write architecture astronaut shit in C# just as much as Java.
The nice thing about Java is the deployment and management tooling. It's cross-platform and mature. C# is not nearly as good in this respect, although with the open-source it is finally free to move with that.
> C# is basically the same thing from a VM perspective, an interpreted bytecoded high-level language, but tied to windows.
C#/.NET hasn't been tied to windows for a number of years now. .NET Core/.NET 5 is cross-platform and great to work with. All of our CI/CD runs on Linux agents too.
The branding has been churned like crazy. As far as I can tell, the first .NET version that officially supported (almost?) the complete API on Linux was released last month, so we’d have to sign up for being an early adopter.
"the complete API" is a bit of a misnomer, since there have been new APIs and runtime capabilities that aren't available to the Windows-only, older runtime (The .NET Framework). This has been the case since at least .NET Core 2.1 but has continued ever since.
The remaining APIs are (mostly) AppDomains, Remoting, Web Forms, WCF server, and Windows Workflow, most of which is either an acknowledged "this was the wrong way to do it so we won't bring it forward" (e.g., Remoting) or tied to Windows anyways (e.g., WCF).
> C# is basically the same thing from a VM perspective, an interpreted bytecoded high-level language, but tied to windows
C# is not tied to Windows, some new features in the latest C# 9.0 doesn't even support running on the Windows-only classic .NET Framework.
All new .NET development + C# features is being invested into .NET 5+ (FKA .NET Core), i.e. the high-performance cross-platform runtime.
> The nice thing about Java is the deployment and management tooling. It's cross-platform and mature. C# is not nearly as good in this respect, although with the open-source it is finally free to move with that.
Citation needed, I deploy my .NET 5 Apps with Linux tools, either rsync, Docker as well as AWS ECS. All clean + simple, only requires a single command to publish your App ready for distribution, that you can either rsync across or include it in the runtime image of your Docker build.
Tried to publish a Java package last week and the whole experience was a shit show, by far the worst experience of all languages where the recommendation to publish a package is to push it to bintray first, make it available to jCenter than sync it to Maven, where you need to get manual approval to include it in jCenter then you need to create yet another account/credentials with a 3rd Party which requires a manual request via a damn Jira ticket. Then each package manager has different requirements as to what a package needs, I could publish it to bintray but couldn't get it to jCenter without uploading a POM which new Kotlin projects aren't created with, then MavenCentral requires a stricter POM and Java Docs but there's no standard way to publish to a repository as bintray needs their own non-compatible task, so now I have duplicated generated POM's in my gradle build to satisfy different repositories, for bintray I needed to hook into their bintrayUpload task and generate the POM just just before it uploaded the package which I needed to decompile its sources to find out where exactly the POM file needs to be written to, no examples of which existed for Kotlin build.gradle.kts scripts that new Kotlin projects are created with. Then there's the case that every build.gradle example uses configuration that is already deprecated and Java/gradle seems to be the only one requiring uploading binary .jar's with your source projects.
Every other language has a single repository you can publish to that you don't need to jump hoops to get, published using standard tools, simple, clean, straight-forward & well documented.
Something C# never was, given that it always JITs before execution and AOT compilation to dynamic libraries has been available since version 1.0 via NGEN.
Plus lots of additional AOT alternatives like Windows 8.x Bartok compiler, .NET Native and CoreRT.
This on top of third party offerings like Mono AOT or IL2CPP, and the research compilers from Singularity and Midori projects.
Whereas for Java, while AOT has been available since around 2000, it has been for the most part only available on commercial JDKs, and free beer AOT only came with the release of GraalVM community, the addition of J/Rockit JIT caches into OpenJDK, and IBM releasing OpenJ9 as FOSS as well.
Agreed C# and Java are virtually identical. However the cultuer is completely different. The plethora of libraries to me ends up being a handicap. We have had a bunch of different Java developers on our project and each one does things differently so we end up with a huge mess. I didn't see such problems in C# world where maybe we just had better devs that concentrated on clean models instead of incorporating fashionable libraries and other moving parts.
How so, I had nothing but issues when trying to deploy cross-platform Java because of the Java ecosystem itself being bad compared to C# or Golang where you just compile stuff and run it.
Its Jira combined with outsourced or contract developers that only care about getting that feature added. Our app is a mess, loaded with technical debt and hugely difficult to support and use. 90% of devs dont care, they do add their one piece of new functionality and move on to the next one or next project.
BTC is so pointless to me. The problem is it keeps going up. It looks like its more likely to hit $100,000 before $0, so you can still make a lot of money by buying now. Which is why I bought some.
I do a lot of both. Excel really is great for data where there are less than say 100k rows. Its just so easy to see exactly what you're doing and what the data looks like. If you have millions of records Python really does better but I still find it frustrating to find a way to keep peeking behind the curtain.
Ideally I'd have a type safe language which can embed data the way excel does. If Excel had dotnet languages instead of VBA and could store data arrays in XLBs it'd slay.
Because poor land use, like monoculture tree plantations, is likely equally as bad as atmospheric CO2 increase for the health of the earth.
Additionally, biogas is at best carbon neutral/slightly positive rather than carbon negative. Since you're still producing CO2 burning stuff, but it does get mostly reabsorbed by plants every cycle.
> is likely equally as bad as atmospheric CO2 increase for the health of the earth.
I'd disagree
> biogas is at best carbon neutral/slightly positive
Of course that's the point - much better than oil/gas/coal. Yes ideally we'd like energy with no downside. Burning renewables is a great compliment to solar/wind.
Absolutely agree, there is no perfect solution out there. However, wind and solar definitely have less of the land use issues that biofuels have.
The farms for biofuels are typically mono cultures, which is going to involve pesticide use and commonly fertilization. Both of which have some significant downstream effects that the world is trying to deal with right now (see the deadzones in many river estuaries, possible insect decline, etc).
Hydro is looked at less and less as a green energy solution because of the significant damage done to river/ocean systems (elwha river restoration, possible klamath river undamming). I don't think there will be any more large dams added to rivers that aren't already dammed in North America.
I'm also not a huge fan of utility scale solar. I understand that it is currently moving the needle significantly since the infrastructure costs are cheaper than residential solar, but there are so many added benefits of residential solar (reduced urban heat islands, no additional land used) that I see it as the main way forwards. I think that the solar power split that we'll eventually end up with is something like 40% residential solar, 60% utility as panels get more efficient.
