jeremydw

Interested in hearing any tales of build vs. buy for CMS. Anyone have anything to report? Medium/large size company usage would be interesting to me.

Sounds like someone has never been asked to clone and run software targeting Python 3.x when their system-installed Python is 3.y and the two are incompatible.

This comment section itself clearly shows how crazy dependency and environment management is in Python. In this thread alone, we've received instructions to...

- poetry

- "Just pin the dependencies and use Docker"

- pip freeze

- Vendoring in dependency code

- pipreqs

- virtualenv

This is simply a mess and it's handled much better in other languages. I manage a small agency team and there are some weeks where I feel like we need a full-time devops person to just help resolve environment issues with Python projects around the team.

Foo Fighters have always meant a lot to me and I am a huge fan of Taylor Hawkins. I’ve been overloaded at work the past few weeks running my company, and have been heavily enjoying Taylor’s side albums these last few weeks.

A friend sent me this poem to help cope with this news, entitled “Encounter”…

—

We were riding through frozen fields in a wagon at dawn. A red wing rose in the darkness.

And suddenly a hare ran across the road. One of us pointed to it with his hand.

That was long ago. Today neither of them is alive, Not the hare, nor the man who made the gesture.

O my love, where are they, where are they going The flash of a hand, streak of movement, rustle of pebbles. I ask not out of sorrow, but in wonder.

                                                        Wilno, 1936

Personally I'd like it a lot. I think applications half of the screen can make sense. It'd be great to use to place things off screen that I may not need to use actively like Chrome devtools.

Accessibility is an issue though. If i could three finger scroll context horizontally that would be nice.

Someone should make a compiler that converts inline styles to Tailwind so then you don't have to learn Tailwind but can still use Tailwind.

For example it can convert `<div style="background-color: white">` to `<div class="bg-white">`. Perfect! (Yes, "bg-white" is the Tailwind way to make the background color white.)

I don't think this is quite right.

I'm not a tailwind user but I think the following:

``` <div class="flex">Foo</div> <div class="flex">Bar</div> <div class="flex">Baz</div> ```

gets generated to:

```html <div class="flex">Foo</div> <div class="flex">Bar</div> <div class="flex">Baz</div> ```

```css .flex { display: flex; } ```

If we replaced this with `style` attribute usage, you'd get:

``` <div style="display: flex">Foo</div> <div style="display: flex">Bar</div> <div style="display: flex">Baz</div> ```

Assuming the content is gzipped when transferred (a good assumption), the non-Tailwind version's payload is smaller because there are no separate CSS definitions.

Your statement is true in the general sense (a page can easily load unused CSS with other CSS/styling approaches) but I don't think it's correct to say that using Tailwind results in smaller payloads vs. using style attributes.

Instead of running Chrome and Chromium, try Chrome and Chrome Beta (or Dev/Nightly)? You can run the same profile in both and have two instances open.

Noticed that keyboard navigation (tabbing, focus order, focus rings, etc.) didn't work on this site. Maybe I'm being pedantic but a baseline for good UX should be accessibility.

Often, it's not the developers that are at fault. Middle managers, cross-functional people, etc. ask developers to cram garbage into otherwise would-be lean pages. Developers often have no authority to push back, and stakeholders often don't fully understand "why" the garbage they're asking developers to insert into pages is detrimental to the user experience.

With AMP, the little badge (the verification), serves as a constraint for developers, but mostly for business stakeholders. The conversation of "I can't do that, because it's simply not compatible with AMP" is way easier than "I can't do that, because it will make the page slow".

IDK. I get that it's a hard problem, but it's a solvable one. It's not like it's some equation or law of science that needs to be discovered. It can be solved with money and effort. :\ I get the economics don't work out in normal times for a reserve like this, but that's exactly what an insurance policy (i.e. a federal reserve of medical supplies) is for.

It's just like nukes. We have a stockpile of them that are maintained... nukes are very hard to produce... etc. etc.

I understand. But, it's about keeping a reserve. On one hand, it's wasteful. On the other hand, a maintained reserve can save lives. This is a problem that can be solved with money.

Planet Money did a great episode recently on how the US government is currently paying for a year-round supply of chicken eggs to produce vaccine for a pandemic flu. (https://www.npr.org/transcripts/812943907).

I understand this situation is different from eggs, as an egg not used for a vaccine can be converted to feed, but in the end it's all about money. It's like an insurance policy. I pay for auto insurance but don't use it until I really need it.

I keep seeing articles like this pop up. During one of the first coronavirus press conferences, the White House invited CEOs from Walmart, Target, CVS, etc. – presumably to show strength of the private sector.

On the flip side, why can't we enlist money and resources from the private sector to quickly fix some of these supply issues? For example:

- Convert car factories to produce masks and ventilators.

- Convert construction companies to build makeshift hospitals. (Or use hotels.)

- Use tech companies to improve national information access with regards to CV19 testing and track and help patients using their software on their phones to help with contact tracing.

I realize that it's not as simple as pressing a button and instantly converting a factory that makes Teslas into one that makes masks. I also realize there are potential privacy concerns with nationalized information tracking.

But, we're about to enter an unprecedented public health crisis. We have resources that can lessen the impact if we just align and get behind this direction.

I can't help but think we could do more and not just wait for the shortage to happen, and for the curve to spike.

We stockpile enough nukes to basically destroy the whole Earth (exaggeration but you get the idea), but we can't stockpile some ventilators and face masks in case of a pandemic? You can't fight a pandemic with diplomacy. At least you can fight a foreign enemy with that.

What is that speculation based on? Why wouldn't Google want more browsers to be able to Cast?

My opinion: I feel like this is a pro-user move with an unfortunate side effect of breaking/unsupporting an extension. If I just want to cast to my TV why should I have to hunt for an extension. I'd rather it "just work" via a context menu in the browser.

Speculation: The production of this page was likely handled by Marketing, which functionally likely sits in a different org within FB and doesn't have access to many eng resources. So, Marketing sees WP VIP as an easy way to get a site up by just running a credit card. Speaking from experience, I think this "outsourcing" is probably good – if there's indeed no engineering team dedicated to Marketing needs like this.

That said, I'm sure WP VIP will break down when Marketing's needs increase – such as when Marketing needs to do internationalization, or perform a timed launch of a new site/content update.

This is how I distribute Grow (grow.io), a Python program. It's worked really well so far, but it's also produced a few issues in development, for me.

For example, PyInstaller itself changes drastically from version-to-version, and I've previously had to spend hours picking away at why "compiled" Grow worked before but no longer works post-PyInstaller updates.

Overall happy though, and much happier to write in Python and distribute a single executable without requiring folks to muck around with Python versions, pip, dependencies, etc.

I can reproduce it. In order to fix it, I have to refresh the page. Happens on my Mac all the time when accessing G+ from a browser window that may be a different size from the browser window I previously used to access G+ in another session.

You can double click in a window's title bar to get (what I think is) the same behavior as in pre-Yosemite versions of OS X.

Generally, on pages/domains where you may provide users with a sign in box (such as the Google Accounts login page), you want to disallow other sites from iframing your page to prevent a clickjacking attack – http://en.wikipedia.org/wiki/Clickjacking

So Google.com busts out of cross-domain iframes by default to prevent attacks like this.

I tried it. Why did they have to send me an email containing my quotes, versus just displaying the quotes on a results page? That seems particularly un-Googley. I hope my email address is not shared with any third parties.

Feedback: It's kind of hard to understand this statement. Your product is basically a client-side API that allows my application to use your API to integrate with a third-party storage service. So "cloud storage will be free forever" means your API is free to use forever for someone else's cloud storage? Presumably you make the code available to the customer to use and then restrict usage/distribution with a license?

A friend of mine is on the team for Kloudless (https://developers.kloudless.com/). I haven't actually used it, but the marketing material tells of the same value prop as your project. Have any quick summary of the differences?

While this doesn't directly pertain to your comment, perhaps it's somewhat related to onboarding with GAE...

I've been developing on GAE since it was released in 2008 and recently became "Google Cloud Platform Certified".

I'm considering offering a "Google App Engine for Startups" class/workshop (at something like General Assembly). The class would primarily include details about the platform's architecture and best practices for building high-scalability apps (like, say, Snapchat) so your app can "scale without thinking twice." Do you think there'd be some interest in a class like this?

Perhaps it's Netflix Open Connect? (http://oc.nflxvideo.net/docs/OpenConnect-Deployment-Guide.pd..., https://signup.netflix.com/openconnect)

I'm building Grow and the Grow SDK (http://growsdk.org) which has a lot of overlap with Statamic (file-based, content in Markdown, YAML things).

One of our tag lines is "develop everywhere, deploy anywhere" – as in, sites are file-based and can be developed locally or in the cloud on our web service. Grow can deploy to a variety of servers (S3, GCS, Dropbox, etc.).

The project's not quite ready for use yet but the SDK will be released as an open source project under the MIT License.

Someone submitted my introductory blog post about Grow on HN a few months ago: https://news.ycombinator.com/item?id=6562182 – Right now you can sign up for the mailing list, and when a developer preview is ready I'll send out updates. :) I hope to have something ready in a few weeks, actually.

I just downloaded it to Glass and tried it out. The UI is nice, and very simple. You say "OK Glass, translate this" and then you point your face (the camera) at some text (there's a bounding box on the display that you put the text into).

You need to hold your head still, and then the software expands the bounding box to the full size of the screen. Everything I've described so far happens very quickly, and then slowly some of the words on the screen are translated and replaced in place. The lighting in my room is not very bright, and so far I've been unable to get full sentences to translate (just words, and just for a moment until I move my head a little), but I suspect it'd work better in high contrast situations (out in the sun, block text, etc.)

Tapping the side of Glass lets you switch between to/from English/Spanish.

Edit: Last thing, IMO, the largest downside to the UX right now is that when you move your face (even a tiny bit) the in-place translation disappears and you need to hold your face steady again to get the translation to appear. This would obviously make it pretty difficult to use in a real world situation (like, if you're walking outside – you'd need to stop and hold very still to translate a sign) but it's still super cool.

OP here. I totally agree with your statement in that it's becoming easier and easier for single developers to build (and launch) something cool.

I suppose I must have glanced over this when I wrote the post, but I'm definitely targeting Grow towards producing content-heavy informational marketing web sites, blogs, portfolios, landing pages, personal sites, corporate information pages, marketing campaigns, etc.

In other words, Grow is great for teams that want to produce and manage stuff like the marketing content you see on https://stripe.com/, http://about.pinterest.com/, http://www.apple.com/mac/, http://www.google.com/think/, etc. I wouldn't recommend using Grow to build your actual product. :)

Often times, coordinating the launch of your marketing content with the launch of your product is tricky, and that's another thing I aim to solve.

Ghost is super cool and I love the UI, but I also find that having a persistent database limits some of the portability. And, depending on what's in the database, it might mean that developers can't use their favorite tools (like Sublime Text, etc.) to author content, develop and design templates, etc.

This is a bit of a shameless plug, but I figure it's relevant to this topic. I just put up blog post introducing my new project, Grow (http://about.grow.io/blog/all-i-want-to-do-is-build-a-web-si...). Grow overlaps with Ghost in some ways, but attempts to be a full-fledged, modern file-based CMS and is not designed just for blogs alone. I've been following all the replies in this thread to get a better idea on what people are looking for, and I think I've nailed it.

Basically, the way I've architected Grow is the whole system is file-based: content is stored in Markdown or YAML files, templates are stored as Jinja2 templates, separate from the content.

When you start up a Grow server for development, essentially what amounts to a super lightweight in-memory index is created from the file structure, and that allows your site to be generated (including pages that leverage complicated queries or access content through taxonomies).

This design keeps everything incredibly portable (zero-configuration development AND zero-configuration deployment) – which is one of the values that I hold to be very important. Anyway, the project is still super young (and my blog post is light on technical details, but I'm working on it), so I'm interested in getting any early feedback.

I posted about this last night, but this discussion is significantly more relevant to my new project, so I figured I would jump in and post again.

This is awesome because it's actually exactly something I'm building – a portable, open source, file-based CMS with a NoSQL document store, backed by Git, hosted in the cloud for social management/deployment, also runs locally. Eventually I'm planning to add easy blogging features for "non-techies" though my initial target audience is definitely professional, interactive web site developers who work with a big team.

If anyone is deeply interested in this space, I would love to learn more about your requirements and share more about my project so I can develop based on real user needs. You can also check out a data sheet I put together at http://grow.io. :)

Shameless plug: Solving high-quality web site production (for a multi-person dev team, including non-developer personas such as designers, content writers, reviewers, translators, etc.) is actually part of a new project I'm working on (http://grow.io). If you (or any other reader) has an immediate need for this type of product/app, I'd love to talk to you to learn more about your requirements (and share more about my project).