Personally, I'd rather have a few extra mm of thickness and batteries that are not glued to a keyboard. Efforts could be made to keep this tech more repairable.
Speak for yourself. I want a thin laptop that feels almost like a slab of mysteriously lightweight solid aluminum, and Apple is delivering that.
It's not like this was a cost-saving measure for them; they're not pulling one over on you. They went nuts trying to make these things solid, lightweight, and skinny, and this was a tradeoff they made --- at significant expense.
It reminds me of printer sales or high-fee consumer credits.. they benefit from consumer myopia about the future. There's even a lot of literature about that:
Does it remind you of buying nearly everything? Do you think the average consumer decides to buy a home appliance or a television based on the possibility of providing user service at reduced rates?
"Efforts could be made"? Which passive-voice efforts do you mean, specifically? Apple has designed their battery to be made up of several curved units that take up all available airspace in the case, and those have to be secured in place somehow, so that they don't rattle around like cheap PCs. Screws are not a realistic solution here because of obvious strictures from the design. A simple one-piece replaceable battery design is simply no longer feasible in this form factor.
So if you think it'd be trivial to make this more repairable, you need to say precisely how.
One of the significant drawbacks to every proprietary drag-and-drop website builder is that you cannot easily export your website. Any time you spend building your site with their tool just further locks you into their hosting platform.
I've seen some very nice personal webpages built on Squarespace, Weebly, Wix, etc. by non-technical and non-design users, but I would never recommend it to a business client.
What about for say a small non-profit that isn't tech-savvy that will have at most 10 pages of content?
I could see where this could really be an issue if there was a lot of content or integration with the website being made. And I suppose too preserving old URLs (if that's something the client cares about)
If they have old URLs you can use the redirects under "Settings" -> "SEO". Oddly placed, but hey, the functionality is there. And for non-techies I think Weebly is wayyyy better than WordPress.
There is an export site functionality which gives you everything: HTML, CSS, images, uploaded files, etc... I'd never actually tried it until now, so thank you :-)
For a website like that, I would recommend a simple Wordpress site on a basic shared hosting provider. It's quick to get set up with the most important information, and then easy to keep updated by multiple non-experts.
Why out of scope? It's a DB api that has no browser/ui dependencies.
I see that the levelDB implementation you pointed to can use a backend that uses IndexedDB. So theoretically this levelDB Api could provide an Api that work across both browser and server.
But argh. IndexedDB is a standardized api. It has a usable open source implementation in WebKit. Why not just go with that?? Why create a different API that does the same thing? I've been building an entire app around IndexedDB, but now I have to port it to a different Api to run on a server? Why?
If you'd used leveldb from the beginning you wouldn't have this problem as it will happily work on the server and in the browser https://www.npmjs.com/package/level-js
Yes I see that. But if IndexedDB were supported on Node I also would not have this problem. So the question is, why can't node just support IndexedDB (which is formally specified in a standards document) instead of inventing an extremely similar but incompatible api?
Because IndexedDB is a W3C spec[0] intended for web browsers and LevelDB is a third-party npm module[1].
Node is just a JS environment. Implementing IndexedDB is as much out of scope as implementing XHR[2] or the File API[3]. In fact it provides the building blocks developers to implement any of these on top of Node should they need to (like node-fetch[4] implementing the Fetch API[5] for isomorphic apps).
This just begs the question. The question is, what about IndexedDB, XHR, the File API, etc. make them unsuitable for pure-JS environments?
Because there is nothing about the problem domains (indexed key/value store, asynchronous web requests, filesystem I/O) that are specific to web browsers.
If a problem domain is common across browsers and pure-JS environments, then it should follow that there can be common APIs. If some part of the API is necessarily specific to one or the other, then ideally these differences should be localized to small parts of the API.
That's an intuitive assumption but it's naive (i.e. it lacks understanding of the actual domain concerns).
JS in the browser needs to be sandboxed by default and has to handle concerns like cross-origin policies and interactively seeking user permissions. It also has some fairly browser-specific singletons (e.g. a shared global cookie storage).
The equivalent built-in node APIs are much more low-level, allowing developers to use abstractions that are useful in their problem domain.
Having an IndexedDB implementation in node core would be an incredibly pointless effort (most apps out there won't use it) and bring with it several complications (e.g. pluggable storage backends and concurrency conflicts if you want multiple node processes to share the same database). Plus it would mean the Node Foundation would have to get involved in the standardization process to make its concerns heard and likely introduces concerns that are irrelevant to everyone else (i.e. browser vendors).
Don't forget that Node is not a web framework. It's a JS runtime environment. It is primarily used for things that talk over the web or that generate content for the web, but it's not at all unreasonable to implement other things in it (e.g. mail servers). The web specs carry a lot of overhead that is simply unnecessary for most node applications even if it is perfectly necessary in browsers.
The only spec I can think of that I'd like to see in node is the Fetch API and for that we have node-fetch, which just wraps node's low-level http module.
What I'm trying to say is that node doesn't need these high-level APIs because it can give you the low-level APIs to implement them with. Browsers can't do this, so they need to work at an entirely different layer of abstraction. Plus node allows you to easily include native extensions whereas in the browser you can't have that (except for NaCl).
That HR barrier is really difficult to understand. There are so many libraries and frameworks these days, and companies are looking for a person with particular experience in a particular combination of things. It doesn't seem to matter if you know similar tech and are willing to switch over.
I wonder how much good talent is never even looked at because of this.
I know there was the developer agent idea (agent like an entertainment agent) floating around several years back. But this area really seems like an industry ripe for innovation. Starfighters.io has a take on the security world, but anyone out there looking for a business idea: there seems to be a large group of talented engineers out there who are being passed over by HR systems today.
From their description I'm guessing Northeast Minneapolis. It is an old blue-collar area currently being revived, and has quite a few older 3-story houses.
A lot of the old warehouse buildings have been gutted and renovated, turned into office spaces, breweries, lofts, restaurants, and coffee shops. Its also considered the arts district of Minneapolis.
I think the crime used to be worse than it currently is, but I'm not certain of that. I started working in the area a few years ago, and I haven't witnessed anything unpleasant. It feels quite safe here.
If you go across the river to North Minneapolis, you'll run into a rougher neighborhood with bars on windows and stuff like that. But even then I've heard things are improving over there too.
Add to that list "Business Intelligence" developer/analyst, although that term is gradually changing into something about analytics and data science, which are demanding degrees in statistics.
The reality is that a lot of "Business Intelligence" work is writing SQL & reports for business types that don't know how to write SQL or don't want to learn.
It means writing a lot of reports, but its a good way to get exposed to a business and yet still be involved with light development. There's room to grow too if you want to learn more about data warehouse design, ETL processes, OLAP cubes, etc etc.
I dropped Dropbox (except for when I have to use it at work).
The tipping point for me was Condoleezza Rice. But there were other issues that were building up. It was consistently eating my laptop battery, and on my desktop with traditional hard drives, it would take forever to start up and finish indexing files.
I replaced Dropbox with a mix of things. My documents went to Google Drive. I converted my old windows desktop into a xubuntu linux home server type thing, and installed BT Sync for the other files I had to sync.
I also do plenty of other things with my home server. Really wish I set one up sooner.
