Personally, I'm a huge fan of Elm. I'm a fan of languages with strong type systems and the functional paradigm is just icing on the cake in this case.
I haven't done too much with Elm, yet, but what I have done, I love it. It's exactly how I'd want front-end web development to evolve into. What I'm waiting for is the day (if it ever comes) that I can have Elm compile to WASM and mostly forget JavaScript.
I agree. I'm also glad they specified "opt-in" consent and not "opt-out." They can't start collecting your data without your prior knowledge and authorization. This is a good thing.
Next step would be to disallow hijacking and data insertion into your stream of data. It would be a step towards cementing ISPs role as a dumb carrier of data.
As a fellow Vim user, I don't use the escape key anymore. It's awkward to hit and I rebind it to "jj" (or more recently "jk"). It's unergonomic to reach for the escape key where it customarily is. If it were where Caps Lock is, it would make much more sense.
That said, I don't like rotating my hand or remove my fingers from the home row.
It's really a non-issue because you can rebind keys so easily, it's not even funny. Everyone seems to be making a mountain out of a molehill.
For sure. I have had a student assistantship for the past three and a half years, but I took a leave of absence from it over the summer to pursue a separate internship in industry (the student assistantship is in academia/federally funded research center). It was great seeing the difference between academia and industry and I'll be graduating in December with my BS in CS with a job lined up in industry.
My student assistantship started the summer after my senior year of high school and I attribute some of it to my prior experience since my high school didn't provide much in the way of CS classes so I lacked a formal education but it wasn't a full time job either.
What type of work do you do exactly? I'm just curious because in my experience, I've never run virtual machines with front ends. As of late, I haven't been running VMs at all and have been using Docker containers on my Mac to emulate the environment I need something to run in.
I also use OmniFocus, but with their infrequency of updates and their lack of Touchbar support, I might be tempted to try out Things 3 and see if it works better for me. Then again, I might just be naively using OmniFoucs, so it might be better to try to modify my workflow before looking for alternatives.
The way I see it, too, is that companies that don't embrace flexible work hours in fully remote companies (as opposed to just flexible working arrangements) aren't really a remote company. They're just pushing off the capital cost of having an office to the employee themselves. It's a pretty dishonest thing to pass themselves off as a remote company if they expect you to work like you do in an office environment.
The flexibility of being able to intermingle personal tasks throughout the workday is paramount to remote work. It totally does reduce stress and it allows you to work when you're productive and not work when you're not. I find that I'm a very bursty developer and I think that's more the rule than the exception in our profession. Remote work arrangements really help accommodate that reality where output is not constant throughout the day.
The closest thing to that would be the 12" MacBook. I really think Apple needs to put the MacBook Air line out to pasture. They haven't updated it in a couple years and it was honestly never that great to begin with.
They should just focus on the MacBook and the MacBook Pro. With the new 13" MacBook Pros, the weight and footprint is getting ever closer to the MacBook Air, so that's also an option.
I went from a 3x24" 1080p monitor setup to a single 34" Ultrawide recently and really enjoyed the move. I'm just as productive, if not more, and having more horizontal screen space makes up for losing the extra monitors. Overall, I would recommend one larger, higher resolution monitor over multiple smaller ones. There's less context switching because you're looking at the same monitor the entire time.
I actually find that unless I do some amount of project management (i.e. use Trello or Pivotal Tracker), I easily get myself sidetracked. I'll use other tools for longer running timelines, but splitting things out into small stories actually helps me stay focused without getting bogged down in considering the implications to every design decision I make.
For a lot of software, making the best decision today without worrying about tomorrow, while still following tried and true engineering practices (i.e. test driving, etc), leads to a project that continues to progress.
They actually don't have an aerospace program. You're right about their mining engineering program. CS has been getting better over the last several years. It's definitely grown. I do agree it leaves something to be desired, but to be fair, plenty of graduates go on to work jobs at prestigious employers because they went for it on their own and picked up a lot along the way. They didn't just learn what was taught in school.
Word on the street was that the new MacBook Pros came with shrunken batteries because they couldn't get the terraced design to fit within design spec (thermals, I think) like they did with the MacBook. Hopefully in their next design iteration, they'll be able to fit a 99.5Wh battery back in the laptop.
The TN, non-retina display on the latest MacBook Air makes it feel neglected by Apple. That screen is also awful to look at and the viewing angles are supremely poor.
If you have a MacBook Air and like it, by all means use it. If you're in the market for a new laptop, don't buy a MacBook Air. It's essentially been abandoned by Apple.
The best answer to your point b is C++. It's shown a ton of adaptation to the times. Almost to a crazy extent as you see tons of new features hit in each standards revision (C++11, 14, 17, etc). To me, it keeps up more quickly than Java.
I would argue that statically typed languages aren't really an ergonomic cost. The amount of testing I have to do to be confident in a dynamically typed language is quite unergonomic. Having to add types is a small cost in comparison to the tests I don't have to write. Additionally, knowing the type allows me to be able to reason better about the code I write; it's more predictable.
Ultimately, I like statically typed languages miles better than dynamically typed ones. They're also more performant and I like that.
Whether or not they benefitted from his actions, he still defrauded them, essentially. The ends should never justify the means. Our legal should not take that into account when assessing penalties.
No, it doesn't. Not through the OEM. The last version of Android was Marshmallow which is two major versions behind the most current.
Sure, you can flash it yourself to the latest version, but there's no guarantee that it'll work. In my book, not having support from the OEM on the latest possible version of Android that can be loaded on your device does not count as having access.
The ideal, here, is that once self-driving cars reach a level where they are demonstrably safer than human drivers, the issue of liability discourages continued use of human-driven vehicles.
The way I see it is that once self-driving cars are safe and viable, anytime an accident involving a human and a self-driving car happens, the human is automatically assigned fault. It doesn't restrict your freedom to drive the car, it just makes you think twice since liability is against you should an accident happen.
This of course, assumes that self-driving cars are capable of driving perfectly within existing driving laws. If that is true, there's no way a self-driving car could legally be at-fault for an accident.
The plan is for Rocket to run on stable by the end of 2018. v0.4 is getting closer and the two biggest features remaining to be implemented for it are connection pooling (which I have an open PR that's being worked on) and CSRF support.
At least in the United States, I had my fair share of issues with my late 2016 MacBook Pro.
First issue was dead pixels on the screen. It was replaced in warranty for free with superb turnaround. Dropped it on a Thursday night and had it back Tuesday by lunch time.
About nine months later, the backlight on the screen died and I had just a black screen. Rather than wait for an Apple Store appointment, I got a box to send it in. The box was overnighted to me and the shipping to the repair depot was also overnight. I shipped it out Wednesday after work, it arrived and was serviced on Thursday, and back in my hands by Friday at 10:30am.
When I got it back, however, the keyboard had an issue that only could have been caused by the repair. I did a walk-in on Saturday morning at my local Apple Store and they started by looking into replacing the computer without me asking.
All of these repairs and replacements were done in warranty or under Apple Care free of charge. The replacement was amazing, too, because it was processed as a return and repurchase. So, I got a brand new Apple Care policy on an upgraded (better CPU, GPU, 1TB SSD) mid 2017 MacBook Pro that lasts the full three years as part of the return and repurchase.
They've more than made me whole and made me better off than before by replacing the computer. I'm definitely impressed with their customer support compared to any other computer vendor.
Things definitely appear to be different across the board for people outside of the United States. All lackluster Apple support stories I've heard originate from outside the US. Inside the US, customer service is great.
For Rust, I'm interested to see what the future holds once the community coalesces around an async IO interface. Additionally, when procedural macros stabilizes (for real), the possibilities for ergonomic frameworks in Rust become endless.
Rocket has been really interesting to work with, but it only works on nightly since it relies on experimental codegen/procedural macro features. Once procedural macros stabilizes, all the codegen can be ported to that. It doesn't support async IO yet, but that's because it's waiting for the community to coalesce before diving into it.
I think there's a future where Rust web frameworks are as expressive as Rails or Laravel but bring type safety and sound, zero cost abstractions to the table.
Additionally, the thought that we're not alone and we're not the most advanced species. If that's the case, then why haven't a more advanced species made contact yet?
That oversupply of talent is also being directed towards 100s of projects that are hoping to be successful. How much of that talent would be better allocated to basic research and discovery? How much further would that propel us if we redirected more of our focus from commercial gains to satiating human curiosity?
I don't see Go as a panacea for opening up libraries for use. You're still going to see languages that can export C interfaces for that. It's going to be C, C++, and Rust that are likely to persist as the languages of choice for massively consumable libraries. As long as they can export a C interface, you can get low (or no) overhead interop. Go's biggest disadvantage is that it ships by default with a runtime.
Ah, I understand now. Yes, translating from a Go implementation to a Swift one would erase most of the complexity of reimplementing the algorithm (in a potentially error prone way).
I agree that once Rust lands async/await and it matures, it could be the go-to for safe, cross-platform libraries. That's my hope, too. I'm selfishly a Rust evangelist.
It should be seen as appalling that the overall wage growth is less than inflation.
Secondly, yes, the absolute refusal to train on the job is an indictment of how the industry views software engineers. Rather than being treated as creative professionals we're treated as assembly line code monkeys. It also leads us to working in low trust environments that like to make us think that we're highly trusted.
I agree. I'm not a big fan of Material design either. Too flat and I find the color palettes a little odd.
One thing that really bothers me is Google designing their iOS apps with Material design rather than using the system iOS design. They just don't feel like they're part of the iOS ecosystem with how jarring their design is.
This seems to run counter to the idea that Google wants to promote democracy. Hell or high water, if a country has stifling civil liberties, a company with real principles in cultivating discourse and democracy would stick to their guns regardless of local laws.
In this case, it looks like a simple case of complying with local laws to continue to growing their bottom line. It’s why we can’t believe Silicon Valley when they say they want to cultivate discourse and democracy. They don’t. They want to make money. When the two coincide with one another, that’s great. When they don’t, profit is more important than freedom. That’s why we can’t trust private enterprises to act in the best interests of society.
I'm actually not advocating breaking a country's laws or their sovereignty. What I was trying to argue (and I probably didn't do a good job) is that trusting a for-profit company to serve the general welfare and public good is a fool's errand. This is further proof that companies like Google only care about furthering conversations insofar as to make money.
It appears to me that a lot of people have shifted their trust to private corporations from government entities. Namely because we've stopped holding our elected officials accountable. There should be and always will be a struggle between for-profit ventures and the general welfare but if we don't have trust in democratic institutions, we'll continue ceding power to for-profit ventures.
With all of these emerging privacy concerns, it reinforces my choice to move away from the Android and Google ecosystem insofar as I can.
It reinforces my choice to embrace the Apple ecosystem. While their products aren't perfect, they do take your privacy seriously and you do pay for it. But to me, that seems like a fair trade. Additionally, they have second to none customer support, so it's going to take a company providing the same level of support (3-5 business day repairs on laptops) for me to move away from Apple.
It's not that he's unwilling to make it run on stable, it's that he has to sacrifice ergonomics to make it run on stable. Despite it not being async, yet, Rocket is my go-to because it has the best ergonomics. Something like actix-web may be more performant, but it's ergonomics are poor in comparison.
Regardless, Rust is stabilizing procedural macros which just leaves the never type as the last stabilization required for Rocket to be able to run on stable Rust. Additionally, I believe their next release is targeting the rewrite to async. A lot of it has to do with Rust firming up its own story around async.
Not to mention that Bitcoin has a very low value proposition outside of being a store of value. I can see a crypto economy where Bitcoin backs the value of other cryptocurrencies, but it’s not a good first-party currency. It’s a mere store of values nd people don’t really agree that it’s useful to exchange for services. They just see it as useful to hold value.
Something like Ethereum, with a real value-proposition, is a more worthwhile cryptocurrency.
Basically, I see crypto evolving into pseudo-fiat currencies with some large financial institution (that isn’t a nation-state) ensuring it’s a valuable commodity. I’m just not convinced we can (or should) escape a fiat-like economic system.
Honestly, the nightly compiler is _really_ stable for the "nightly" moniker it receives. It's basically just the rolling release of the current Rust codebase each night. I've run into issues before where I get an internal compiler error, but those have been rare and rolling back a version (or waiting to roll forward) resolves them.
For the most part, there's very little risk running Rust nightly and in fact, that's my MO. I like being able to receive the latest benefits and opt into compiler gates and whatnot. I couldn't do that on Rust stable.
Overall, I feel very little friction sticking with nightly rust and using libraries that are still nightly-only.
If I were to change careers, I think I’d go into politics and become some type of political operative. I like the process, I like the issues, I like the strategy. It would flex a completely different set of mental muscles than my software engineering job and to me, that would be quite a welcome challenge.
It takes something to realize you may have over generalized. Thank you for the apology. I appreciate interactions like these on the internet as opposed to animosity.
I don't really care about the headphone jack, but I wish they'd just make the phone thicker to accommodate the camera bump. In that extra volume, just fill it with a larger battery.
With their laptops, I enjoy the form factor, but it's really Intel's fault for not delivering the low TDP, low wattage CPUs they promised years ago. The old MBP form factor feels too thick but the battery life of the new ones is disappointing. I actually don't mind the butterfly switch keyboard and like the lower travel distance. The old keyboards felt too mushy.
I haven't done too much with Elm, yet, but what I have done, I love it. It's exactly how I'd want front-end web development to evolve into. What I'm waiting for is the day (if it ever comes) that I can have Elm compile to WASM and mostly forget JavaScript.