throw868788

10 ms·

31.
by throw868788 5y ago
While there are upsides to compulsory voting this is one of its downsides IMO. Because you can't "refrain to vote" the parties know all they have to be is slightly better than the alternative and they will get your vote. In s
32.
by throw868788 5y ago
Reified generics avoid a lot of "boxing" that comes with standard Java, and that's only one of many features there that helps. Its just easier to avoid allocations in .NET in general over Java IMO. From recent articles and im
33.
by throw868788 5y ago
I just looked at the F# vs Java benchmarks and .NET is still faster on most of them just to get a sample on more idiomatic code. The F# codebase doesn't use a lot of externals looking at the code list https://benchmarksgame-
34.
by throw868788 5y ago
Not a dumb question at all. You can to an extent, but the returns diminish quickly. It isn't linear. This fact however makes "performance per watt" comparisons misleading between different processors designed for different en
35.
by throw868788 5y ago
I do feel this is something that should be made illegal. In many countries it is a breach of your employment contract to diverge your pay, unionise, etc. However it is ok for employers to share data with each other, even if they don't
36.
by throw868788 5y ago
They are working in .NET 5 last time I checked. Opened an FSX script, "#r: nuget SwaggerProvider", point to a JSON API and it seems to work with IDE auto complete included with 2 lines of code, no project scaffolding, or package m
37.
by throw868788 5y ago
They got type generators which somewhat influenced and predates the Source Generator feature by a few years. Not the same thing of course, and from what I've seen are slightly different in target/scope. (e.g. F#'s seems more
38.
by throw868788 5y ago
Maybe try F#? I know it isn't always an option but if you can, especially recently, its been quite productive to work in.
39.
by throw868788 5y ago
I don't think F# is that second class anymore especially if you are developing on Linux/Mac OSX. The more concise language/syntax is a big plus when you don't want the heavy IDE and want to be cross platform. The VS Code
40.
by throw868788 5y ago
Agreement or disagreement - my point is each company does both good and bad. What people choose to see is somewhat colored by your previous position/bias just like everyone else. Will be the devil's advocate here. Microsoft advanc
41.
by throw868788 5y ago
To be honest out of the big tech companies which one is not there to "screw users" as you put it? Especially the ones that depend on ad revenue. - Facebook: Their users are their product. There's enough evidence to show how t
42.
by throw868788 5y ago
Agree with this. What's more interesting is on the feature level languages do borrow/converge on each other in order to try to secure a position in the market. I note that as an example Java is consdering a .NET like Span feature
43.
by throw868788 5y ago
Just like any other human made structure even outside of programming I've known. Admittedly I think the foundation is mostly independent from .NET and is around open source projects in the ecosystem limiting the damage this could cause
44.
by throw868788 5y ago
Where required there are ways to force it to inline/devirtualise yourself. For example using refied generics is one way I've seen - i.e. there is no interface/virtual casting since it takes a type that implements interface, r
45.
by throw868788 5y ago
I never buy into the tech stack argument that things are being worked on (e.g you mention Project Vahalla but I see this across many languages and tools). Seen this argument used on a number of different technologies. It compares a future s
46.
by throw868788 5y ago
Agreed; especially since it didn't have it originally. I'm sure some compromises were made to do it in a way that fits into the execution model/doesn't cause regressions to older code. They are both good languages for su
47.
by throw868788 5y ago
In my experience that isn't quite true. You usually OO for IO/interop if a C# library is being used, then its module code for the most part all the way down (e.g. ASP NET Core define a class for the controller, then have it intero
48.
by throw868788 5y ago
Its still nice to have shared memory especially in a functional language where due to lots more immutability it isn't as big of a price (i.e. more concurrency safe). Especially if your sharing in-memory caches and the like. I've s
49.
by throw868788 5y ago
I've seen both being used by hedge funds and finance/banks actually. A lot of F# use anecdotally is closed source finance (this has changed now I think) which is why IMO it didn't have as much open source visibility or people
50.
by throw868788 5y ago
The real reason is to attract and onboard people onto the platform. Part of me always felt they should of just put a functional wrapper on their APIs, have an API that avoids the mutative fluent interface, and then just show some F# example
51.
by throw868788 5y ago
A bit late but I can comment to be informative. > I'd need to see evidence, it's hard to believe .NET can offer anything more performant than say Vert.x or Micronaut :-) Benchmarking is interesting because it depends on your ca
52.
by throw868788 5y ago
I think there are factors to consider one over the other; just like sometimes OcAML could be a good choice as well. I wouldn't dismiss F# for production use however having seen it used successfully on large things in Windows and Linux
53.
by throw868788 5y ago
I like OcAML as well - in fact I stated that. The original reply was to a comment comparing OcAML to F# in the context of adoption in a company to a risk adverse poster worried about costing the company "mega dollars", where one r
54.
by throw868788 5y ago
>That's not necessarily a positive. Our job is to deliver business value, not follow the latest fashionable trends. Just to clarify latest trends don't mean untried tech, it sometimes means just new features of existing product
55.
by throw868788 5y ago
Sure - those applications generate C# code in the background so that's that. Its not that F# couldn't do it, but the no language that's coded by a human competes with auto-generated tooling backend (XAML to C# form code). XAM
56.
by throw868788 5y ago
I don't think the risk is that bad. Especially if you are using .NET Core as a cross platform target most of the tooling is made for Windows anyway so is mostly unaccessible. VS Code for example works reasonably as good as any other VS
57.
by throw868788 5y ago
As someone who's used both I generally am not as big of a fan of OcAML where it matters - usage in most companies and projects. Sure it has some features that are nice but often they are "nice to have's", whereas the F#
58.
by throw868788 5y ago
Why not both? Seen that work quite well.
59.
by throw868788 5y ago
All languages have their issues though, and they all make different tradeoffs. After using a number of languages compared to say C#/Java/Scala/Ocaml/etc I don't find F#'s limitations that crippling. In fact I t
60.
by throw868788 5y ago
Let's be honest. IMO the assumption of Australia being an island was right (as evidenced by the states that made sure their states were islands most notably WA). At this stage WA is clearly the "gold standard" of COVID manage

More ›