I think it's an inner join, not a cross join. SelectMany() produces a cross join.
183 karma · joined December 19, 2014
I think it's an inner join, not a cross join. SelectMany() produces a cross join.
same here. And regardless of what their codebase smells like, their stuff works and does what it says on the tin, letting people play whatever format there is out there on a massive amount of different systems. I'm the first to admit the dialogs they're using to configure the codecs is one which is a yearly 'Ugliest UI' award winner, but luckily others have made front ends which make you avoid all that mess in the first place.
In the decades I'm developing software, I've learned that there is no developer out there liking somebody else's code. There's always something. You can think you're objective and unbiased, but you're not, no-one is. FFMpeg's code might be a mess due to a large chunk of legacy / backwards compatibility code, but very likely the other side's code base is a mess in other people's eyes.
> Companies that need enterprise functionality around security and flow configurability move to Github Enterprise and spend, not $7/month/organization, but $20/month per programmer.
This is not a given at all. Github is used by many because it's a great free service. When you have to pay for the service however (or better: you're going to use a service offered by github which costs money), there are other alternatives which might be cheaper or even free. E.g. private repositories are free on bitbucket. Private repositories don't need the social aspects of github at all, as they're private and the group of people using the repo is limited and known up front.
I find the article missing this point as well: sure they got funding and that's great, but their popularity among the users of the free service is not a reason to think they'll be a very profitable company: only the paying users can make that happen.
So let's accept that as a baseline? Why is that even 'normal' ?
It's my PC, not theirs. I licensed the OS, but I didn't tell them to do any other thing. My PC is connected through routers which at least for the first hops I control myself, how is it then 'normal' I still am not able (!) to stop an outside company from peeking into what I do on my pc?
That could get interesting: Google, using the argument that all those ad-related scripts make things slow, ranking sites with a lot of them lower than sites which don't, and at the same time hitting their competitors hard: after all, Google makes money through ads, if their competitors are forced to be used less (by Google's own actions) more people might be using Google ad networks.
Not sure if this will work, I thought about this years ago when I was still in the demoscene but never had the time to implement it.
1) The site still talks about carburetors and has no mention about fuel injection systems, while in Europe all cars sold must have a fuel injection system for quite some time now, so this looks quite outdated
2) Diesel engines of course don't have spark plugs, but you don't mention diesel engines.
I think with 'go' as a language when you start with it, there's a lot to love: things are simple again; "Look ma, a real program that does something with almost no code and also no magic shit behind the scenes!". But things are always simple and nice in the beginning, when you are focusing on just a small part of the complete picture.
The problem with 'simple' is that unless it abstracts away all complexity you'll ever need to deal with, you'll need to do a lot of work yourself: it's the typical RISC/CISC argument from yesteryear: do you want a small instruction set which is simple but results in a longer program, or a complex large instruction set which results in a smaller program?
So, to be able to deal with all possible complexity in all possible scenarios, either the language has to be vast in its expressiveness (go isn't) or it has to come with a vast standard library which offers additional expressiveness through classes / methods / functions / subsystems or whatever the language is lacking, OR you have to write it all yourself.
In the end, the net-result is the same: the system as the end result of your work is the combined complexity of the code written by the developer(s) and the complexity of the libraries used. Go doesn't change that, it just moves the divider between 'own code' and 'libraries' more towards 'own code', even if that's simpler to write because the language lacks things which some people might consider 'oh god this is complex, I'll never understand this'.
This is an extensive list of (non-MS) OSS libs and tools for .NET , complete with descriptions. The URL might suggest this is the .NET source, it's a set of text documents with URLs to OSS libs/tools.
It's the same with all software, really: to be able to do a large scale project you have to have funding from somewhere, as you need developers full time working on it to fix/write the stuff no-one wants to fix/write. Some OSS projects get this funding indirectly by sponsored developers who work at company X and write OSS code all day for the project (this is what Linux uses). Other projects are funded by VC money, licenses, support contracts or ads. It's not common a large scale OSS project is successful and stays successful without any funding from the outside.
Thus, if a piece of software gets its funding by selling licenses (like with Hyperdex Warp), it's the same as with a company getting funding by sponsoring: if the cashflow stops, the show ends. In the case of OSS you can grab the sourcecode at least, but in the end, to successfully maintain that it takes a lot of effort most of the time, as the projects are often large, complex and the internals unknown to the user.
Without telling you.
So if the movie isn't based on her work, how can it be seen as a result of the contract she signed?
Though it might indeed be redundant, as designing the algorithms and understanding they'd work is enough: typing it in and seeing it work is an exercise performed so many times it's become a chore.
This means that all the fun of exploring and adventuring to get from A to B is more or less gone, as you already know what lies ahead and how to avoid it. You _know_ what's coming and thus how to deal with it. You also _know_ which parts are a chore and can suck the energy right out of you. This alone can make a journey that would otherwise be fun, a problematic undertaking we probably would like to avoid if we had the chance.
The post absolutely doesn't state you should avoid crap, it also doesn't state one can achieve greatness without avoiding mess and misery. It just writes about by learning a lot over the years the adventure of a journey from A to B is fading away and with it, the fun and excitement.
The post hit home with me a great deal as it perfectly answered why I didn't code on a Saturday anymore (e.g. silly stuff like a small game or tiny tools), but only program software during work days and only for work: it wasn't a problem to find ideas to write a silly program for, it was the baggage that came with it as I already knew I had to do X and Y to get started properly, Z to get something on the screen, get a lib for E and F and as I knew that would likely be a chore I wouldn't even start, as: why bother with chores on a free Saturday if you can have some fun?
It's still possible though, don't think it's all grim and gloomy and dark, you just have to put what you _think_ up front what could happen aside and still do it. You'll learn it isn't so bad, but sadly the fun of adventuring and exploring into new territory is often not there anymore, simply because it's familiar territory. That's often a good thing in life, but if it's adventure and excitement filled exploration is what you're after like all those years ago, you're not going to find it (easily).
Cheers :)
Now, windows server 2012 R2 on the other hand... aargg...
It's not only a trend among average consumers though, it's also sadly a trend among us developers: not a lot of developers are willing to spend even a single dollar on software they have to use every day. "Do you have a free version?" "Why do I have to give away the application I spend years full time on writing? Do you work for free?"
I don't think this will end well. If we less and less value software on its true worth, it will become less and less attractive (or even possible) to write the software we need in a society which more and more relies on software. Watch this great presentation by Erik Meijer [1] where he addresses this problem (and others ;))