...it will compile your project with dotnet bundled together. So you don't need to "install" dotnet on the destination systems running your program.
It worked on some Debian and CentOS/cpanel servers that I have (never installed dotnet on them).
That command alone gives you a whole directory of files that you need to deploy. But I think it's also possible to have to completely bundle all of it into a single file.
I really wish they put more priority on bringing discriminated unions into C#.
Seems like the most significant thing they could do.
I've spent so much time looking into using languages like Rust, Haskell, F# pretty much just because I want a compiled language with DUs. But always lose interest due to more practical requirements like tooling and package ecosystem.
If C# had them, I could stop looking. I would basically use it for pretty much everything except web stuff. And that's coming from someone who used to be very anti-MS. To me C# does everything I want in a language, except for lacking native simple DUs.
There's lots of cool things I've learnt about in FP languages. But discriminated unions are really the only feature that I feel like I'm really missing out on in other languages.
> I strongly believe that functional programming is not a good fit for 100% of software architecture. The best is some sort of hybrid.
And yeah I agree with you. FP is awesome at many things, but not everything. I went down the FP rabbit-hole, it was a and I had many revelations. But once the excitement wears off, I realised that I still like using classes for some things that are just inherently mutable... e.g. GUIs, and progress bars, SQL transactions etc.
Not to mention that being able to type `someObject.` and then get autocomplete for all its methods is a huge time saver, and something that is quite a lot more painful with pure FP where you're much more reliant on your memory and looking things up to find all the functions for something.
I think Rust did really well in balancing the two. I just want Rust's simple struct instantiation and enums in C#, and I could stop wasting time looking for the mythical "perfect language".
You may be interested in (for example) the approach taken with Halogen, the PureScript web framework. Every widget on the screen has its own state and actions, widgets send each other messages, etc. It ends up being very "object oriented" in a way that you're suggesting, but it also is very principled, i.e. components send each other messages, do not have access to each others internal states, etc. This gives you a really good way to separate concerns, while having each "widget" have its own state/not having to have a single global state a la elm.
Why oh why are people still putting special characters in the names of programming language?
# . + are bad enough... but * ?!? It can't even be used in filenames at all.
And while Google might be ok at indexing it... pretty much every other fulltext search engine will be useless. Not to mention it can't be used in package names, domain names, filenames, and a heap of other things.
Even an emoji (while still terrible) would be better under some circumstances.
"Go" was ridiculous enough, ironically from somebody who works at Google. But these people still putting special characters in the names must really not care about findability/disambiguation at all.
PHP might have got a lot wrong... but the name is great... it's just "PHP" everywhere, even the filename extension.
I think there's three different potential points/statements:
* a) The main overall productivity issue
* b) Making a more general point that they don't seem very bright, at least compared to former colleagues
* c) Specifically mentioning IQ score
Yes even though the main topic is (a)... b/c is just extra context.
I think OP's goal was to make point b/c to give some further context on their perception of the situation (whether it's true or not doesn't matter, the point is explaining what they think).
Sure both (b) + (c) especially can make you look like a dick, but I don't think making the (b) point is totally irrelevant to the overall post. It at least gives us more insight into what OP thinks, even if they're wrong.
So perhaps going the (c) route (rather than b) was just an attempt at trying to be slightly more objective (even though there's obviously no evidence at all). (b) is vaguer than (c), so I don't see that (c) was completely irrelevant, even though it comes across arrogant.
I sent them two separate questions months ago, and never got responses to either of them.
Annoying, as I'm a paying customer.
And right now I'm trying to update my payment method, and there doesn't seem to be a way. So should probably just cancel entirely.
Their https://forwardemail.net/en/my-account/billing page seems buggy too. I'm only seeing an invoice from many months ago, even though there's been payments since. And it says my next payment is Sept for some reason, even though it's billed monthly.
Yeah I find that this style of cheat sheet where it's overlayed on a keyboard aren't really that useful when you know what feature you want, but don't know the key.
They make more sense for reverse-engineering, i.e. you accidently just hit a key, and you want to find out what it did.
I guess they still are useful to study in one big go, when you have some time to sit down and purely just study + practise keybindings (not working on real code) and helps with muscle memory kind of thing.
But less so when I'm being impatient and just want to figure out one thing that I need right now (while working on some real project).
Is Google using JS for the backend ad serving / AI?