mradmin

Can you give some examples of why the nodejs community is not nice?

Let's not forget about http://prototypejs.org/ & http://script.aculo.us/ for modern Web 2.O

Sure, could be. I guess i'd expect Microsoft to have company-wide processes and practises when working with OSS though. Could be wishful thinking.

Seems like a mistake to me. Microsoft recently adopted one of my Open Source projects and part of the agreement was they would keep the original license. This was a request on their part, I had no choice in the matter. They know what they're doing, I don't think they would do this deliberately. (Licence here: https://github.com/microsoft/vscode-gradle/blob/main/LICENSE...)

Here's an example using GitHub Actions: https://github.com/badsyntax/docker-box/tree/master/examples...

Agree the traefik config is a little complex but otherwise it works great for me. About using portainer, it's useful for showing a holistic view of your containers and stacks, but I also use it for remote deployment of services (Eg as part of CI/CD). I'll push a new docker image version then I'll use the portainer webhooks to redeploy the service, then docker swarm takes over.

My anti-kubernetes setup for small single servers is docker swarm, portainer & traefik. It's a setup that works well on low powered machines, gives you TLS (letsencrypt) and traefik takes care of the complicated network routing.

I created a shell script to easily set this up: https://github.com/badsyntax/docker-box

Can you run microk8s or k3s on a single server/device? Even if you can, seems like the wrong tool for the job with unnecessary complexity...

This is the approach I use, but I've always found some sort of issue in every generator I use. A valid openapi spec does not imply a generator will be able to handle it. You'd think have a specification would mean the generators are "bug free" but it's not the case, and bug reports are lost in a sea of issues: https://github.com/OpenAPITools/openapi-generator/issues so i don't see things improving anytime soon.

I've also wondered if the "logic-less" template approach is the right approach for these generators. You can't fix bugs or add workarounds just by providing a custom template, you need to change the underlying Java code to provide the correct data models to the logic-less templates.

Some of these are multi-liners that can be converted to one-liners. For example I believe "npx" can be used for all the node examples for example "npx http-server -p 6007 ./root"

[edit] ahh i see this is called out in the gist comments

There's also some wacky code in the HTML. Check out the body tag:

  <body class="post-template-default single single-post postid-4483 single-format-standard bridge-core-1.0.6  qode-title-hidden qode_grid_1200 footer_responsive_adv qode-content-sidebar-responsive transparent_content qode-child-theme-ver-1.0.0 qode-theme-ver-18.2 qode-theme-beatportal disabled_footer_bottom qode_header_in_grid wpb-js-composer js-comp-ver-6.0.5 vc_responsive &quot;&gt;&lt;noscript&gt;&lt;iframe src=&quot;https://www.googletagmanager.com/ns.html?id=GTM-WVTMQP&amp;user%5BisLoggedIn%5D=0&amp;&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;display:none;visibility:hidden&quot;&gt;&lt;/iframe&gt;&lt;/noscript&gt;&lt;br style=&quot;display:none;"  >

If it's not clear, all that code is within the class attribute!

It's "an hour a day(+/- 10 minutes)" which I read as "an hour a day give or take 10 minutes"

(deleted)

I was expecting something more like Gorce (https://gource.io/) that shows contributions via commits but this is rather cool nonetheless.

Staticman is awesome for static websites! (next.js, jekyll etc). It provides user content via pull requests. That's all it does! This means you have complete control over the UI. No loading of 3rd party scripts etc.

I wrote a blog post about integrating it into Next.js: https://richardwillis.info/blog/self-hosted-staticman-dokku-...

I don't understand the title. Does the OP not understand the difference between Europe and the EU?

> You'd use it where you'd use REST/API/JSONRPC/

Not really. You'd use it for inter service communication but can't really use it in the browser (see grpc-web)

I live in Barcelona (expat). On the "main" beach (Barceloneta) you'll find full on nudity, mixed with tourists, families and others who aren't nude. The thing is, truely no one cares. It is so not sexual, and i am yet to see someone treating it as sexual. I don't ever see people recoding the nudity. Every beach I go to along the coast here (and up the Costa brava) I find nudity. Young, old, male, female, you name it. I expect to see peni, balls and breasts any beach I go to. I don't know what it is about this side of the world, but nudity is still completely separate from sex. No one will bat an eyelid if you decide to go nude. This is maybe a generalisation but after almost 3 years I'm yet to see people complain or be uncomfortable about the nudity here. I don't really have another other point, just mentioning my observations.

I can't speak from experience with regards to this particular approach, but I've worked with css-modules with webpack (css-loader), and debugging the class names is no problem at all, CSS source-maps point to the source, you can view the source code within your developer tools. It shouldn't really be any different than debugging Sass generated CSS, for example.

I assume soucemaps would solve this.

This website made me totally lose the plot, while attempting to spot the drowning child from the beginning of the video after refreshing the page.

Here's an even more minimal seed project i've been working on (with sass): https://github.com/badsyntax/react-seed

GWT pronounced «gwit»

Seriously? First I've heard this is how you pronounce it. And how does one pronounce gwit? I think I'll continue to call it: G.W.T.

Is IE11 really considered "old"? IMO, these fixes need to be released for IE11, because flexbox is supposed to work in IE11.

I'm working on a project that uses flexbox heavily and the layout was not tested in IE during the development process. (I guess the developers assumed IE11 was modern enough!) I joined the project late, and my task was to get the layout to work in IE11. Oh my what a task it was.

Anyway, here are some bugs I found (specifially related to IE11): https://gist.github.com/badsyntax/6eb3a74d35e52373c17c

Whoa this brings back some memories! I was mostly a Fast Tracker user though. I used to love spending hours downloading .xm's at my dad's work so I could rip the samples and use them in my own tracks.

Regarding image sprites, if you're using a CSS pre-processor, like Sass (with Compass), then auto-generating sprite images and associated classes is trivial and adds little to no complexity or maintenance.

It's slow for me also on Chrome 35, but i can't jump to any assumptions on why, without doing the proper debug. For example, the home page is loading a video and adding syntax highlighting to code examples, which can also be slow. Also the UX can be improved using [unresolved] on elements: http://www.polymer-project.org/docs/polymer/styling.html#fou...

Slow UI or slow loading? Slow loading is due to all the HTML imports generating HTTP requests. This can be optimised by inlining the web-components, using a tool like https://github.com/Polymer/vulcanize

I'm not sure why the polymer website is not optimised like this.

[edit]

Here's what vulcanize does: http://polymer-twitter.badsyntax.co:8002/build.html (Code here: https://github.com/badsyntax/polymer-twitter)

Concatting styles is a whole different story, conceptually it doesn't fit in with encapsulated compontents.

What if you had a requirement to create variation styles of those elements? How would you do that? Would you add you base style in your id selector, and then variations with classes? Again, you'll face specificity issues with that approach. Keeping things simple is the best approach here IMO. I've done a heck-load of CSS and have seen how hacky a stylesheet can become because of specificity issues. Sticking with classes and keeping selectors short will make your stylesheet easier to follow and more maintainable, but this is just my approach!