What do you mean stay up to date? From my experience I've noticed that if they dig deep and understand the underlying fundamental concepts of the trade, there's not many programming problems, platforms, or languages, that couldn't be learned in the span of a few days. The longer I go, the more I realize that everything that seems new and fresh was most likely already invented in some capacity before I even wrote my first line of code. I completely understand if they are non flexible and still choosing out of date frameworks or libraries that aren't necessarily used any more, however the ability to compare and contrast frameworks and languages and choose the one based on a deep understanding of the underlying implications seems to me more important than being fluent in the latest platforms.
Fortunately, you can buy a dongle that will hold the airpods together if they do happen to fall out. You connect the dongle to the phone via a small wire that you hardly notice.
The problem with that is, there's only one thing, some product manager somewhere, that sits on a light switch of your company or project's success or failure. They could even unintentionally end you with a price change.
I do appreciate the rule set that Rust forces the programmer into, however I keep coming back to it felt to me that I was being asked to conform to the language. Maybe I'm looking at it all wrong. When I was also learning other languages it felt to me some of them conformed to me more than others, and therefore were easier to write logic towards. Is low level safe systems programming the main/only use case or is there a reason to use Rust in other domains?
Can I easily replace systemd on a distro that came with it? I wouldn't consider myself a Linux expert, but I got to a point where I could get around and started to understand the different init runlevels and how to set them, then everything was ripped out from under me and I no longer understand how to work everything anymore. Perhaps Linux boots faster now, I don't know, but it was really very frustrating I couldn't find a major user-friendly distro that worked the way I was used to.
You are correct here, but the question is, is there a flaw in the Apache License then? Should it also include the patent grant for non-derived works, as long as someone adheres to the license?
It looks like there is an unintended consequence of the Apache License 2.0 of allowing a company to patent some functionality, and the only way to acquire that patent is to keep your implementation as a close fork of the original derived work. The question is, whether or not the patent grant for just using swift (downloading and running it), can cover other development work that is not associated with swift. If not then Apache License 2.0 actually seems to paradoxically reinforce the situation it is trying to avoid by tying implementation and copyright directly to patents, thereby boosting patents as a way to squash other open source projects. Any comment by an Apache person would be greatly appreciated.
I believe there is a flaw in the Apache License 2.0 here. If the patent grant only covers the code in question. If this is true, then it not only reinforces software patents, but reinforces implementations too.
You know what. I looked again at the license. I think this is the first time I've noticed a flaw in the Apache 2.0 license. I think you are right. Derived works is described as: "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof."
--edit-- see below comments.. this may not be so simple.
No. The Apache License 2.0 does not work that way. You are allowed to copy and use everything in the Swift language to your own liking in a similar manner to the MIT and BSD permissive licenses. However if you then try and begin a lawsuit against Apple for anything in what you copied, your rights are terminated, therefore invalidating your suit. The Apache License also gives you access to the patents in the language. It's a bit of a hack like GPL is, except that you are allowed to do just about anything with the code except sue.
The license, at least the way I see it, is a signal that Apple isn't in the business of patenting language features. In fact, in a way, Apple is using their resources to gobble up space that patent trolls can never again exploit. Once a patented feature is released under Apache 2.0, I know of no way that it can be undone.
POSIX is similar to what you describe. It's a unified paradigm that wrestles the complexities under one paradigm. UNIX philosophy of each tool doing one thing, and doing it well, combined with the constructs that are provided through shells such as inter-process communication and piping everything has turned out to be quite the solid foundation for software development. I'm not saying we couldn't learn lessons from Pharo, but that I'm not so quick to dump everything else to live inside their bubble just yet.
I've yet to use a Vim emulator that worked as well as Vim though. The amount of features in it are mind boggling and replicating that would be the work of a large fully funded team.
It feels like an alien world moving into the Smalltalk live environments and the patterns I've built up over the years and tools like Vim, etc are indispensable when it comes to moving around and modifying code. Of all the reading I've done on it, the entirety of the language is contained inside images. I know that the Pharo guys have engineered this marvel, and I think it's on the verge of a breakthrough with a lot of people if they can ease into it somehow.
"Everything's an object" is object oriented programming done right and I can see why Ruby and other languages used those ideas from Smalltalk. I couldn't understand the fascination with the integrated environments though. It was my biggest stumbling block. Is there a pathway to use Pharo with my traditional tools?
Soccer has headers and the occasional accidental clash of heads. The youth organizations have mostly all banned headers up to a certain age. To be honest, I'd be fine if they banned headers in the game completely if it became an issue. Even then, the ball is lighter than it used to be, so it's a difficult thing to track if headers are still an issue. Technology and rule changes could almost fix it completely. But not sure how they're going to do that for gridiron football and still retain the essence of the game.
I think there's more to it. Ruby, to me at least, seems objectively more difficult to understand intuitively when scanning the code. Maybe it's just a superficial lack of knowledge on my part, but my brain makes base assumptions on how code should work, and whenever something magical happens, it's cool, but slows down the cognitive understanding enough that it seems to me to be a net negative. There's a crossover point where verbosness becomes too much to grok as well. Maybe spending more time in the language raises the bar enough to then become massively more productive. I'm assuming this is the case with Ruby, but I've not given it enough time to make that determination. Python, on the other hand, is immediately understandable to me, and I can jump in and be productive with no previous experience in the language and just an open webpage to the documentation. To each their own, but this is a continuing question for me. The perfect example I think is Perl 6. To me, when I look at everything they're doing in Perl 6, it really does look like the next generation in languages. It's got so many good ideas and insanely helpful constructs. However I'm not so sure if the ability to do things cleverly is a benefit. I look back at Python and see how simple it is and how productive I can be in it immediately and ask myself.. what's the catch. I'd like to use these complex languages for fun's sake, but the alternative is very, very, intuitive.
Popular ideas in UFO circles are that there was a crash, the govs have the tech, and the craft we usually see are replication vehicles attempting to test out what we gathered from the real one that crashed years ago.
This is true if you are running into people on such a basis that it becomes cumbersome. It may be a cultural/geographical thing, where in the US there's ton's of space and in some areas, especially rural ones where you see more small talk, it's possible that you don't see anyone for days at a time, which means you run into your neighbor and the small talk is a way to prime up a conversation. The more dense the population the more cumbersome this type of behavior becomes. The larger the countryside, the more likely the people are going to be using small talk to break the ice.
Silence is great, but there's something more to small talk than just filling silence. Small talk primes the pump for some good conversation. I can't tell you how many times I've come across great conversations and tidbits of information that I'd never have if I didn't chat up with some kind of nonsense to start the conversation. Or alternatively if someone else didn't. The initial part of the conversation is useless, we all know that, but it's a handshake of sorts to see if there's a possibility of a good exchange of something more. If the other person doesn't want to talk, then a quick canned response is the equivalent of, "Hi I acknowledge you, but I don't want to talk right now.". There's a protocol. If the person wants to talk they'll give the canned response, with an added tidbit that can be grabbed onto for further conversation. People are usually just going through their day on autopilot, waiting for a opportunity to connect with someone.
From that link. Holy cow: "“Looking forward for reusability, we don’t believe it really, really counts unless you can turn it around rapidly, or almost as rapidly, as you turn around an aircraft,”.
I had no idea they were aiming for this level. That is just mind boggling how drastic a change it's going to be.