I think that the parent is talking about how much power Google has over mail delivery within its own system, which encompasses a larger number of people. If Google decided to switch to a non standard protocol, then smtp'ers would be left high and dry as Microsoft and Yahoo possibly follow suit to maintain an advantage.
Speculation of course but it does point out the problem with Google becoming too big.
I think it's the overhead of the call or maybe their distaste for the state of repair of OpenSSL, e.g. Heartbleed, that drove them to it.
Alternatively it could just be the chance to write some crypto in Go assembly and have it be included in their code base.
What if we could design a solar cell that could shift from transparent to opaque on demand? Instead of putting up blinds, simply move a slider or tap a button or what have you, and suddenly the amount of light coming in is dimmed, and the energy being captured is increased.
Seems like a win-win to me, if it were possible.
I would recommend employing the Agile approach to development. Create and test a wholly working prototype of whatever you're working on, be it a new feature or extending a function. The key is that the prototype should not by any means be the final product, instead aim to create something that is working and accurate to a small step of the problem; an iterative approach to development. This way, your tests grow with the functionality of your code and if your code is well tested, it should function properly at every step of the way. Thus, by the end, you have a fully implemented whatever that has solid tests and should "Just Work".
If this seems too slow or tedious, you can take the move fast and break things approach, in which you simply create a rough prototype of how you think the code should look, and work through the bugs until it does what you want. You should still write tests, especially to help determine when you've properly fixed the implementation. Keep in mind this involves a stronger sense of underlying problems in bugs and needs good debugging skills to be effective. It can take more time though if your initial prototype is too far off.
Some people think it's a warrant canary of sorts, trying to convey a message that the project had been compromised and was subsequently shut down. But that's all speculation without any evidence to back it up so we may never know.
I dislike Apple, their products and their "you're unique just like everyone else" mentality but i honestly want them to make this move and do it well. They might make an over priced, marginally better EV but more importantly they will drive interest in the technology and the products, leading to faster and greater adoption as well as serious industry commitment which will push for research and development and massive improvements in the industry. Just like they did with mobile phones. I love Tesla but they're the Palm pilot or BlackBerry of EV. Trend setters who will maybe get overshot.
Your hot-linking cross domain made this impossible to try, as I block this. Please serve your javascript directly, even if it is a third party library.
Additionally, the "Over" button (;) does not work for me for whatever reason. Firefox 30.
It does not compile because of the header =\ I tried and even though it can be forgiving of null characters, it definitely doesn't like the stray bytes.
Location: Indianapolis, IN
Remote: Yes
Willing to relocate: No
Technologies: C / C++ / Java / PHP / C# / Go / ASP.Net / SQL / Linux / AppSec / REST / APIs
Résumé/CV: https://larssorenson.com/docs/resume.pdf
Email: lars@larssorenson.com
You can visit my webpage (https://larssorenson.com) for links to my GitHub + LinkedIn for my in depth details.
Frankly I would be excited to see a relief for our energy crisis fuel exploration of "the next frontier." It really is the future of humanity to perfect (or at least improve upon) space travel, even if only for industrial purposes, and having a (sort of) realistic goal that will return profits could very well be the spark we need to get support behind it from budget writers.
I like the compiler hitting the website to download the registered characters and if no internet access is available "making it appear to be your fault"
This strikes me as something that should have been a law since day one. We have checks and balances (and we can argue their effectiveness some other time) between the different branches of government, yet when it comes to the police departments (under the executive branch) there is no check or balance when the police departments screw up like when someone in the federal government screws up.
tl;dr: We need to have this law in every state.
I think the article misses the point of why piracy was a big thing. It was not always (necessarily) about getting what you want free of charge, but the free flowing access to the media and content. For instance, the reason Game of Thrones is watched via torrent downloads more than via HBO is because a large portion of the audience wants to either just watch HBO or just watch Game of Thrones. But to do that, you have to have an HBO subscription through some cable provider, who does not provide a direct subscription for only HBO. Thus, if all you want to watch is Game of Thrones and nothing else, your only option is to torrent/pirate it.
The problem is that Computer Science has not been able to mature enough to split programming/Software Engineering into another, separate degree. You do not need a PhD to become a Computer Scientist. If you want to do research and development for a company, it helps but is not necessary. Academia does require it, but that still is not a restriction. See http://en.wikipedia.org/wiki/Whitfield_Diffie one of the co-developers of the Diffie-Hellman key exchange. He never achieved a PhD, yet helped break ground in crypto.
I understand what you're saying, but I think that my point is still valid: If you want to offer a degree to become a Software Engineer, it should be a Software Engineering degree program not a Computer Science degree. Someone else mentioned that the direct path to Applied Mathematics takes form of say an Engineering degree. They are two separate degrees/programs yet clearly Engineering is just the fast path to a career in Math in an industry environment. So too should a Software Engineering degree be a fast path to a career in Computer Science in an industry environment.
Yeah but you'll notice that it is a separate degree and program, targeted for a career in industry applying the math. There are no "alternative" Math degree programs to make better Applied Mathematicians, because they realized that you cannot give someone a Math degree to be an applied mathematician without all the theory behind it. Hence, Engineering, in your example.
I'm rather frustrated with this huge push to create a "new" CS degree, which is basically saying "Let's abandon half of CS and focus on just programming." Computer Science is, obviously enough, the science of Computers and computation. Coincidentally, programming happens to be a tool for computer scientists to interact with computers and demonstrate computational theory. While I understand and appreciate the necessity for good programmers/developers, people seem to miss the point of what a Computer Scientist actually is. It includes a whole lot of theory and knowledge of how computers function and operate, from the fundamental logic up to the application layer. Programming is learned as a Computer Scientist not necessarily for the purpose of a career, but rather as a means of implementing and testing theories and ideas. Much the same as Mathematics where theories are abundant, many of which are necessary to become a mathematician. You don't see anyone trying to create a Math degree that skips a lot of theory and just teaches you Applied Mathematics for a career. While the analogy breaks down when you move into industry, the concept is the same. If you are pursuing a Computer Science degree, you must become a Computer Scientist. If you want a more objective approach, see the definition of Computer Science as put forth by wikipedia: http://en.wikipedia.org/wiki/Computer_science . You'll notice that Software Engineering is but a subset of the field of Applied Computer Science, which is itself a subset of Computer Science.
Before I continue ranting I'll just summarize: You cannot forgo or severely reduce the extensive amount of theory behind Computer Science and churn out Computer Scientists. It does not match up. If your goal is instead to produce more software engineers / programmers / developers who are not real Computer Scientists, then you should re-name your degree and your program. You might find CIT/CNIT/IT more appropriate. https://en.wikipedia.org/wiki/Information_technology
The day I can run Visual Studio on Linux to develop a C# app / website I can deploy, run, and test in Linux is the day I forgive Microsoft for their recent issues. They definitely seem committed to turning over a new lease.
I have a touch screen Lenovo laptop I bought my freshman year of college and I put Mint on it. Works pretty well for what I want to do with touch, I can take notes and it supports pressure sensitivity. I haven't had the chance to get my hands on a Pro to test Mint, but that would be my go to.
I'm rather annoyed with mozilla/firefox pushing for ubiquitous usage of their authentication platforms. I prefer my decentralized, modular, and personally controllable account information. The reason I don't "Sign in with Google" or "Login with Facebok" is the same reason I don't want a Firefox Persona or Account.
Also, let me sign up without a damn e-mail.
Interesting, I was not aware that this sort of situation could spring up. But I don't think this should be a reason behind retaining criminalization of marijuana. To those who tout "Free Market" and "True Capitalism," it should be plainly clear that hemp should be allowed to fill the market if it can provide a better or comparable product at a better price. While I don't necessarily think we should necessarily promote a free market economy, I definitely think that marijuana legalization should not be hindered by the potential "negative" drawbacks such as these. Worst case, the government should focus its efforts in regulating prices and uses for marijuana plants, similar to how they regulate/subsidize over-farming.
Very eerie. Scary to imagine that the very systems we rely on are fundamentally flawed even more so than generic "NSA back doors," but down to policy of implementation.
That does pose a problem. I guess given the situation this is definitely an improvement, but seeing the underlying workings make it seem pretty easy to implement in other technologies, given the simplicity.
I'm more interested in the underlying API than than the node package. Apparently it accesses your profile publicly, so there's no magic here, just an API to construct the right URL. Maybe if it worked with a private diary it might be more useful.
Yeah I noticed that as well. Hadn't heard about either, so I'm pretty stoked to see what will happen with them. Pond definitely seems interesting, because it'll be easier to pick up and integrate, plus it has the benefit of solving the first contact problem, with no real key exchange prior necessary.
I wonder how this will be able to be exported/imported.