> I understand that you don't like writing YAML, but to be honest, it's not that complicated, especially if you use our VS code extension (it autocompletes and suggest all the properties, validates the config file, and give you on-hover documentation).
I think you've missed the point entirely. Just because _you_ do not find it complicated, doesnt mean others wont. This comes across dismissive, people dont want to use your flavor of YAML and have to install a VSCode extension to do so effectively. This alienates a bunch of people that dont use VSCode, and who would rather utilize a safely typed library that provides autocomplete out of the box regardless of which editor is being used. IaaC/S should move on from thousand long lined YAML files that shoe-horn in extensibility and composition in favor of using tools (programming languages) that support this out of the box. These libraries could output YAML files for the sake of compatibility.
i’ve been working on a web-framework for Deno called "cobain". would be cool to work with someone on it, and be able to bounce ideas off of.
what separates this web-framework from others (aside from the grunge and punk aesthetic) is a heavy focus on function composition and developer experience. without much effort, as a developer you will be able to deploy your app as
- lambda/serverless function (deno deploy compatibility),
- standalone monolith
- microservice
in addition, i created a small concept of a templating engine similar to swift-ui and react called "peep" that doesn't do anything special syntax wise (its just JavaScript for real this time).
the really awesome part is that the web-framework and the templating language use the same pattern for "decorating" functions utilizing a deep-safe-map builder-like dsl. (which im currently struggling with) to avoid accessing and setting already previously used keys.
i think the most appealing part of this is the opportunity to break fresh ground on a javascript runtime that will likely be used in the next 3-6 years.
you can contact me on GitHub or my email on my profile.
unless i haven’t read deep enough into that groups thread. this seems overblown. alert, prompt, etc. isn’t being deprecated on the entire web, only in the context of cross-origin iframes.
that being said, this post definitely strikes a chord with me. instead of adding a new index of deprecated features, it think it speaks more to the fact that caniuse needs to rethink how they approach deprecated features.
i’d like to think if Apple allowed the AppStore to be an interface/gateway to other stores, most users would be happy. similar to how RSS works, but it keeps it unified for the user.
as many people have mentioned before, one of the main reasons people choose iOS is that it removes the choice and worry about unintentionally installing malware.
opening up the AppStore like this i think would allow Apple to ease up a bit on the gouging they’ve been doing now and instead become a pro-active leader in creating a specification/platform that others can adopt.
what a dramatic and ridiculous statement. i suppose you could say i have a vested interest in holding an opinion like that. however the dude that posted that tweet is in the tech space, therefore (imo) excludes him from being “just a user of the internet”. furthermore, REAL USER demands and expectations increased from native mobile app usage, so of course the complexity of pages/apps on the web have followed suit.
One thing that really bugs me about CommonLisp, is that docs for the supposedly popular libraries are often broken, because they relied on a 3rd party service QuickLisp. A great example of this, is the linked “Clack Getting Started Guide” in the article isn’t even referenced in the clack library repo. This guide than proceeds to link to the broken QuickLisp docs. It’s madness, especially for people that WANT to help move this language forward and increase adoption.
Do you mean Quickdocs? That was a passion project of someone who decided to stop maintaining it. It’s open source and can regenerate docs to be up-to-date. The author simply decided he doesn’t want to maintain it anymore due to other life/health circumstances.
Quicklisp has nothing to do with documentation. That’s a distribution mechanism.
