Its not too complicated but it is an annoyance. I want /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf, /etc/rc.local and all the standard stuff to work. The heavy lifting is done in the kernel. All they need to do is leave it alone. Its getting harder to make Ubuntu behave like Linux.

We also have an “anti-overtime” rate: past twenty hours a week, people can continue to work at an hourly rate of 50 percent. This allows us to have a high hourly rate for the highest leverage work and also allows people to work more per week if they wish.

Most users frankly don’t care how software is packaged. They don’t understand the difference between deb / rpm / flatpak / snap. They just want a button that installs Spotify so they can listen to their music.

Frankly, if the Ubuntu Desktop team “switch” from making a deb of Chromium to making a snap, I doubt they’d switch back. It’s a tremendous amount of work for developer(s) to maintain numerous debs across all supported releases. Maintaining a single snap is just practically and financially more sensible.

This example of the chromium really shows that unless snaps or other similar format was used, applications would have to be sometime very heavily patched to work on older versions of systems to the point that it generates so much work that it would not be worth do to it otherwise, or at least not worth when the snap option exists and doesn’t require that much more work.

What’s the use of ie. snap libreoffice if it can’t access documents on a samba server in my workplace ? Should I really re-organize years of storage and work in my office for being able to use snap ? A too high price to pay, for the moment.

I - we all - totally agree about the benefits of snap for developers. But the loss of comfort and flexibility for end user is eventually a no-go option.

Users want work be done. Not struggling about how allowing access to removable medias or such a file on another partition… Not breaking their habits or workflows each time a snap replaces a deb.

Saving form data across sessions — what do people hate more than filling out a form? Filling out a form twice!

People really don't stress enough the importance of enjoying what you're programming. It aids creativity, makes you a better teammate, and makes it significantly easier to enter a state of flow. It should be considered an important factor in choosing a web development framework (or lack thereof). Kudos!

May I ask what is holding this back?

Making UIs with Svelte is a pleasure. Svelte’s aesthetics feel like a warm cozy blanket on the stormy web. This impacts everything — features, documentation, syntax, semantics, performance, framework internals, npm install size, the welcoming and helpful community attitude, and its collegial open development and RFCs — it all oozes good taste. Its API is tight, powerful, and good looking — I’d point to actions and stores to support this praise, but really, the whole is what feels so good. The aesthetics of underlying technologies have a way of leaking into the end user experience.

And then it will help you choose a specialization in the field that you like.

Find Your Passion, Then Monetize It The

Try a little of everything, and then choose a specialization. Money is not the most important thing. You need to LOVE your activity! But you don't know what you like until you try it.

I personally think that starting from google's components makes easier to keeping update to material specs updates.

If you want a reference to the global object that works in any context, you can read this from a directly-called function. const global = (function() {return this})();. This evaluates to window in the browser, self in a service worker and global in nodejs.

I open this issue to announce that i'm actively working on a rewrite of this library to accomplish these goals:

Microbundle also outputs a modern bundle specially designed to work in all modern browsers. This bundle preserves most modern JS features when compiling your code, but ensures the result runs in 90% of web browsers without needing to be transpiled. Specifically, it uses preset-modules to target the set of browsers that support <script type="module"> - that allows syntax like async/await, tagged templates, arrow functions, destructured and rest parameters, etc. The result is generally smaller and faster to execute than the esm bundle

The use of __proto__ is controversial and discouraged. It was never originally included in the ECMAScript language spec, but modern browsers implemented it anyway. Only recently was the __proto__ property standardized by the ECMAScript 2015 specification for compatibility with web browsers, so it will be supported into the future.

Since I closed down the Dish, my bloggy website, five years ago, after 15 years of daily blogging, I have not missed the insane work hours that all but broke my health.

We don't have clear visibility on which issues the VSCode team is planning on fixing & we would like to avoid duplicating work.

Throughput in Planned vs Unplanned Work: The graph to the left is even more interesting as it contains the initial hints at what’s actually happening. That graph measures throughput with an emphasize on unplanned work. Now, what’s unplanned work? Typically, everything related to features or improvements is planned, whereas bugs, re-work, and service interruptions are unplanned. Let’s see why unplanned work is relevant.

I've only done components that need to/can be Svelte-ified. For some things, like RTL and layout grid, you can just use the MDC packages.

This is Sass based, and therefore doesn't require Svelte components

There are a few intentional behavioral differences between Dart Sass and Ruby Sass. These are generally places where Ruby Sass has an undesired behavior, and it's substantially easier to implement the correct behavior than it would be to implement compatible behavior. These should all have tracking bugs against Ruby Sass to update the reference behavior.

In principle, this information is already available through other means, but it is actually a fair amount of work to gather it in this form, and I think it could be useful to open it up to programmatic consumption.

anything that makes you lighter helps create the balance which keeps you going.

Please don't copy answers to multiple questions; this is the same as your answer to a similar question

Focus on your application: forget about forms details like I'm dirty, field touched...

You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?

If you want to implement a form with a superb User Experience, you have to take care of many variables:

Form validation can get complex (synchronous validations, asynchronous validations, record validations, field validations, internationalization, schemas definitions...). To cope with these challenges we will leverage this into Fonk and Fonk Final Form adaptor for a React Final Form seamless integration.

Managing Form State (holding field information, check if a control has been touched, if the user has clicked the submit button, who owns the current focus...) can be tedious and prone to errors. We can get help from React Final Form to handle these challenges for us.

This implementation is based upon following sources: JavaScript Debounce Function by David Walsh Lodash implementation

Once again, this isn’t good or bad, it’s just the most efficient way to create something that is similar to something else

I'm okay with an overall design that allows people to plugin the parts they need in order to be able to generically support a compile-to-javascript language, but to bake in support for one singular solution because its popular is simply bad engineering.

This is the problem with baking in support for frameworks with special cases in the codebase. You can never support all the frameworks. :-(

Other frameworks, which use a template syntax built atop HTML — Svelte, Vue, Ractive, Glimmer etc — have historically been fragmented, meaning those tools need to be reinvented many times.

Every new variation to the view requires updating both the view model and the template. This holds true even for simple variations.

It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.

"Protestant" life of wealth and risk over the "Catholic" path of poverty and security.[8]

Almost every social network of note had an early signature proof of work hurdle. For Facebook it was posting some witty text-based status update. For Instagram, it was posting an interesting square photo. For Vine, an entertaining 6-second video. For Twitter, it was writing an amusing bit of text of 140 characters or fewer. Pinterest? Pinning a compelling photo. You can likely derive the proof of work for other networks like Quora and Reddit and Twitch and so on. Successful social networks don't pose trick questions at the start, it’s usually clear what they want from you.

If there was a place I thought reactivity would be weak, I embraced it and I worked on it until I was happy with the results.

Although I also work with solid in my day job at inrupt, I wrote this guide in my spare time.

Because I haven't worked with React Native, and so I'm not a specialist in it, and developing a React Native version of this package would better be done by someone being an expert in React Native.

. They built great houses, bred race horses, and accumulated slaves, sometimes holding twenty or more bondsmen

I’ve written for 15 years, 569 essays, and 2.9 million words and counting. You can read a quick intro or my best work, which I curate below.

no one wants to feel like their time is wasted

There is this black hole syndrome where you spend hours working on something and get no feedback.

export let client; setContext("client", client);

Rollup builds atop Browserify and Webpack's lineage to make it possible to easily consume those packages, while looking to the future of JS modules.

There are work arounds, but nothing clean. I just feel like this should be functionality that should be part of the slot feature.

You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)

I'll work on a preliminary PR (which I expect will need some love from maintainers, sorry!)

This leads to web developers at every company needing to rebuild every control from scratch. This represents millions of dollars of investment for each company to duplicate work that many other companies are also doing.

Modern view libraries like React allow teams to build and maintain these components more easily than ever before, but it is still extraordinarily difficult to do so in a fully accessible way with interactions that work across many types of devices.

It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs

Please focus on explaining the motivation so that if this RFC is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.

First class TypeScript support means that both of these two systems do a good job of handling TypeScript code.

There’s a lot of value in slow thinking. You use the non-lizard side of your brain. You make more deliberate decisions. You prioritize design over instant gratification. You can “check” your gut instincts and validate your hypothesis before incurring mountains of technical debt.

If ADHD is not a disorder, but a mismatch with a human environment, then suddenly it’s not a medical issue. It’s an issue for educational reform.

Thus could Ken Copeland write in his Laws of Prosperity, "Do you want a hundredfold return on your money? Give and let God multiply it back to you. No bank in the world offers this kind of return! Praise the Lord!” In this mentality, tithing is a financially responsible thing to do. It’s a show of faith and a shrewd investment alike, a wager on the idea that God acts in the here and now to reward those with both faith and a sufficiently developed work ethic.

Our company is remote-first and will always be open to employees to work anywhere in the U.S. (or the occasional trip abroad). We made this decision with a great deal of intention because we believe creating and nurturing a remote culture is a key to inclusion.

Ohhh, never thought of this hypothesis: that the act of getting drunk together might be a social technology that helps us verify the trustworthiness of others by inhibiting their higher cognitive functions and thus making it harder to consciously fake things.

having a completely distributed team can make it very difficult for team members to get to know each other on a personal level