lookingsideways

HACS works in a container, or is there specific functionality of it that doesn't work? I've been using it inside a Docker HA container on a Pi without issue.

From the OP:

> Of course I'd like a static website for deploying, but I'd love a web gui which acts as a frontend for such generators.

If you want such a gui on your local machine you're not much more than a few commands away

  npm i -g ghost-cli
  ghost install local

Have you looked into doing just that? There are a number of options and more arriving all the time.

https://ghost.org/docs/api/v2/gatsby/

https://ghost.org/docs/api/v2/eleventy/

https://ghost.org/integrations/netlify/

I'm in the same boat, I much prefer the feel of the butterfly keys to the older mushy-feeling MacBook pro keyboards. Currently I'm still using the first Touch Bar MBP from 2016 and have had zero keyboard (or other hardware) problems.

That was the case with the 2016 and 2017 models of 13" MBP w/touch bar - the right side had reduced PCI Express bandwidth. The 2018 model has full bandwidth on all ports.

It's subjective but I believe it. If remote work is set up well then there is much less emphasis on meetings and much more focus on good written communication. With remote teams distributed across timezones with their own work schedules, async communication is key and systems get developed to allow that. When it's part of daily work to ensure everything is designed and specced properly, communicated well, and there's mechanisms in place to keep the team in sync then it's much easier for management/product to also stay on top of what's happening without endless meetings.

Built-in commenting is planned as part of the Memberships & Subscriptions feature[0]. Ghost needs a robust visitor authentication system for native commenting to work well and that will also involve a big concept-shift for Ghost's front-end from static generation to each page load potentially being dynamic.

In the meantime, Discourse[1] and Talk[2] are great options that can be self-hosted if needed and integrate well. If you look at them you can see the level of effort that is required to do commenting, moderation, and spam protection well at scale.

[0] https://forum.ghost.org/t/memberships-subscriptions/377 [1] https://www.discourse.org [2] https://coralproject.net/talk/

It's an interesting idea but Ghost is a primarily self-hosted application with a non-technical user base. The freedom to swap out or add core dependencies like database servers isn't really available in that environment.

I'm probably biased as I work on the admin interface day-to-day but technology-wise it's been great.

Upgrades are painless, typically requiring around an hour at most. If there are bigger framework changes we can usually upgrade immediately then clean up deprecations later as necessary but even then the work is normally minimal. When there are more stylistic changes that touch many files it's usually very quick work thanks to the codemods that are released alongside. All of this despite huge and continuous under-the-hood improvements in Ember since we've been using it.

Compared to what I've seen in other frameworks I think we've benefitted a lot in being able to spend pretty much zero time bike shedding which libraries will make up our core framework. We also save a lot of time not needing to upgrade disparate parts of a custom framework built of 3rd party libraries that aren't necessarily in sync with each other. The Ember addon ecosystem has also been stellar, with common solutions rallied around by the community such that they are usually as stable as core and kept up-to-date with the latest idioms without breaking backwards compatibility.

In conclusion Ember has allowed us to focus almost entirely on product rather than framework. It stays out of the way and provides very clear happy paths for typical workflows whilst allowing us to break out of those where needed without sacrificing any tooling or upgradability.

As for the downsides I think the biggest has been the limited pool of contributors. A lot of react bandwagon jumping has happened since we started with Ember and it's interesting when talking to other developers outside of the Ember ecosystem because there's a lot of historical and outdated views about what Ember is and isn't. The Ember core team and community is working hard to improve Ember's marketing message to counter that but it's tough to break through when the framework's core selling point is consistency through hype cycles.

From the "unusually fair billing policy" section on the pricing page:

> Our plans are limited by how many readers you have, and how often they visit your publication. We only enforce these limits on a 3 month rolling average, so we'll never make you upgrade plans if you happen to have one big traffic spike or particularly successful month.

> Another thing I don't like about this "forced HTTPS" is that mandatory HTTPS makes it difficult to publish stuff to the web. You must either deploy your own Letsencrypt to run your website, or if it's too much of a hassle (which would be the case for most people, even developers), just run your website on a service provider that already has HTTPS.

> This means people will rather publish their blogs on sites like medium.com rather than running their own wordpress server, or even a ghost blog.

I think we'll just see an evolution of the tools available. For example, Ghost's CLI install already sets up letsencrypt for you along with auto-renew of certificates, anyone using that or the 1-click DigitalOcean droplet will get HTTPS with no extra setup difficulty compared to a non-HTTPS version.

Ghost renders static HTML and includes relevant cache headers on it's responses so if you have a cache or CDN in front then it's pretty much indistinguishable from static HTML :)

As far as I'm aware Ghost runs fine on OpenBSD, we've certainly had users running it on OpenBSD in the past. If there's a specific problem that's preventing it from running for you please open an issue :)

It's not just Discourse and Ghost. Wordpress has been doing this since way before those projects were started and there's no sign that they're going away any time soon.

I had this issue with older versions but I've been using Atom as my primary editor on a rMBP for the last couple of months with no CPU usage issues.

> I need a REALLY GOOD reader. I wish I had a lightweight, clipboard-sized, hi-rez, B&W, PDF reader with the flick scrolling, pinch resizing, etc. of an iPad with the battery life to last a whole delayed flight from San Francisco->Tokyo->Singapore, door to door.

Have you seen the Sony Digital Paper System[0]? It seems to fit the bill perfectly but the price point high.

[0]: http://pro.sony.com/bbsc/ssr/product-DPTS1/?PID=I:digitalpap...

> Bulletin board system gains nothing from "single page application" style architecture, it is a collection of documents, stick with it.

I'd have to say the Discourse project (http://discourse.org) provides a fantastic counter example to this. It shows what can be achieved when SPAs embrace the URL and a lot of thought is put into how the modern browser features can be used to improve the user experience rather than just jumping on the bandwagon.

Example forums:

http://meta.discourse.org http://discuss.atom.io http://discuss.emberjs.org

If your API supports it you can use the EmbeddedRecordsMixin[0]. In general though, what would be a sane default for handling multiple REST API calls to single-model endpoints?

[0]: http://emberjs.com/api/data/classes/DS.EmbeddedRecordsMixin....

If you're on OSX, try it out in Apple Maps, I find their 3D views superior to Google's and it's been available in more locations that I've looked at.

On the iPad you also get more control over viewing angles, I was surprised that you lose that on the desktop.

  - inventory is limited? which amazon website are you visiting?

The amazon.es selection is much more limited than amazon.co.uk's selection. I typically end up buying from the UK and having it shipped across as it will usually be cheaper despite the extra shipping charges.

I was pleased to find they all work in Safari 6.1. In Chrome it's only the regions example that isn't working.

Are you able to upload a screenshot of the aliasing problem somewhere?

Running on a retina MBP, both Safari and Chrome render the text pin-sharp with no noticeable aliasing.

This is the norm in the UK too for shared housing. You have multiple named tenants on the lease and each is responsible for the full rent if the others can't pay.

I saw exactly the same thing. The older logo was definitely clearer in that area.

> Merge all those together, serving up 80 separate assets is insane. Isn't it?

That's what happens by default when using the asset pipeline when in the "development" environment, it's supposed to ease debugging and works well when only including a few JS files. In "production" all the files would be merged into 1.

There is a flag "config.assets.debug = true" in the "development.rb" file, switching that to "false" will output just one file.

Do many of the major sites actually use StatCounter though?

Akamai's stats show a very different story - http://blog.cloudfour.com/explaining-the-ios-and-android-mob...

http://www.netmarketshare.com

Mobile browser share

    Safari:  66.2%
    Android: 19.4%

Mobile OS Share:

    iOS:     65.7%
    Android: 20.2%