The syntax is only difficult to read in their example.
I fixed their example here: https://programming.dev/comment/12087783
The syntax is only difficult to read in their example.
I fixed their example here: https://programming.dev/comment/12087783
I'd recommend removing as many variables as possible.
Try getting a single html page to work (no mongoose, no preact, no vite, no tailwind).
If you can't get that to work, then no amount of tinking in preact/vite/tailwind/mongoose will help you.
Once you have a single page running, you can look at the next steps:
For scripting: try plain js, then js + mongoose, then preact + mongoose. If a step fails, rely on the step before it.
For styling: try plain css, then a micro css framework that doesn't require a build step (e.g. https://purecss.io/, https://picocss.com/), then tailwind if you really want to try messing around with vite again.
Oh cool, yeah and you're also using multiple repeating-radial-gradient
s to generate textured noise.
That's exactly what I was doing while working on a new button style.
Some gradients and some noise sprinkled on top to remove some of the flatness, but while I was experimenting with the noise I happened upon that really cool pattern and thought I'd share it by itself.
Lol, well I could change it, but it was based on the gif at https://quietkit.com/box-breathing/
I think it's because you're not supposed to expand your lungs so much that they feel like they're going to burst.
But if you scroll to the bottom of the css and look at line 69, you can change transform: scale(90%);
to transform: scale(100%);
to see if you like it better.
There's absolutely a massive internal bias people have where they naturally believe that others develop the same kinds of content, when really it's half working on page based content, and half working on component based content.
Both are correct.
The real problem is developers thinking that there are only two methods for making styles: external css files, and tailwind/atomic styles in class names.
Component developers should have their styles inside their components, but not inlined in style attributes (like in tailwind).
Component developers should instead place a style
tag inside their component that is scoped to just that component.
So let's say you're making an accordion component.
Make your html+js/jsx like you already do, and add an "accordion" class to your component's root element. Now add a style tag in your component with a single selector targetting the .accordion
class. Now you can use nesting to style anything in the accordion exactly how you want. Want to style something based on whether an element is open or not? Use an attribute selector. Want to style something based on whether it's child is doing something? Use the :has()
selector. etc...
If you're making a widget system, use container queries. If you're making a card system, use subgrid.
There's so many obvious use cases that modern css provides for, so use modern css! and not any of this BEM or tailwind nonsense. Now your css is so much smaller, robust and more maintainable.
Follow up questions:
Q: But I don't know modern CSS
A: Learn, it'll be much better for you in the long run compared to using tailwind, then needing to learn something else once people switch off tailwind for something else.
Q: But wouldn't putting a style tag in every component mean that there's going to be two style tags on the page if I put two of the same component on the page?
A: It'll only do that if you make it do that. Most component based frameworks are already set up to reduce repetition, check your framework's docs. (e.g. react's many css-in-js solutions, web component's :host
selector, vue's <style> and <style scoped>
elements, SSGs like Eleventy have Asset Bucketing, and even native html is getting it's own solution this year with @scope
).
What do you mean by:
There is no way to split a tab into windows in VSCode.
Do you mean, drag a tab out of a window to create a new window? Because if so, you can do that in vscode.
This seems a little meh, people shouldn't be getting taught react or nextjs if they're not proficient enough with JS first.
That just teaches people to reach for frameworks when what they're trying to do could likely be solved in a few lines of code.
Your question:
what things did the LHC discover that have real practical applications right now other than validating some hypothesis
Is really multiple questions:
Is doing fundamental research with no application in mind useful?
Has the LHC led to practical applications usable today
The answer to question 1 is yes.
There's different types of research programs made to target different goals. Some aim for short or medium term applications, and others are just pure fundamental research.
Just because pure research doesn't have an application in mind, doesn't mean it's not useful. The application isn't the goal, the expansion of our knowledge base is. Everyone who ever thought up of an application for something did so based on their own knowledge base. If the knowledge base never expands, then we run out of applications to think up. This is why pure research is useful.
And all of history supports this:
The answer to question 2 is also yes:
The obvious ones are:
It sounds like to me that you've taken your knowledge of your commonly used languages for granted, and assumed a new language would be just as easy. But if you watch a developer who is dipping their toe into that ecosystem for the first time you'll find them making mistakes and running into footguns you didn't know were possible.
Regardless of the language, not having a proper guide leaves devs susceptible to the incorrect blogospam that's out there, where engagement is rewarded over correctness.
Ignore all of the blogospam.
The two things you need to know:
Here's my shortened version of number 2.
The beginning:
The false start:
The resumption:
async
/await
/Promise()
syntax sugaring, to make asynchronous programming easier...
(rest/spread operator) syntax sugaring, to make destructuring and variadic functions easier??
Nullish coalescing operator syntax sugaring??=
/&&=
/||=
Logical assignment syntax sugaringThe current state of things
Language-wise
Runtime-wise
Standard workflow
Tooling wise
For your simple fibonacci example:
console.log()
and see result in browser's console.Deno.serve()
and see result in network requests/responsesconsole.log()
and see result in terminalI'm curious why people would downvote a request for port forwarding?
I had no popus using uBlock Origin on Firefox
Watching web developers react to this change on mastodon has been... interesting to say the least