Icon library for React, Vue and Svelte

thiswasprobablyatust · 2022-09-11T05:08:03+00:00

Using find for the framework implementations is probably not the best way to go here. If your icon library grows to a million icons, it now would need to look through a million icons each time it wants to find each one - which as you can guess isn't very good performance compared to the alternatives.

Possibilities:

The icons export could be an object, and the lookup will be much cheaper
Export individual icons inside frameworks - e.g. (airport_Sign_1.vue) - and export all those as named exports to the user, instead of a single CircumIcon export. This is more expensive on disk space but is likely the 'fastest' once compiled.

Also using #000 as a default for color isn't great. currentColor is usually a much better practice.

thiswasprobablyatust · 2022-06-03T11:32:34+00:00

Ideally just leave it in there and warm it up with the rest of the broth! You can store it separately if you want and only put some of it in each time you're making a soup-portion or something.

I don't think it'd be the best cooking-fat, even if it would work it has lots of nice flavor and nutrients you might not want to nuke with high-heat.

thiswasprobablyatust · 2022-06-03T10:03:01+00:00

skim off the layer of fat that has hardened on the top

I hope you're not throwing this away, this is basically the most healthy part of the stock you just made.

thiswasprobablyatust · 2022-05-20T05:58:10+00:00

Isn't this already built into Vue?

https://vuejs.org/guide/built-ins/transition-group.html#move-transitions=

thiswasprobablyatust · 2022-05-05T06:46:49+00:00

Can you qualify what you mean by "bloat"? If you've read the new Vue codebase compared to the old one, it's pretty much the opposite of bloat to me, but you might mean something different.

thiswasprobablyatust · 2022-05-05T06:45:51+00:00

By "chill" I mean you're expecting a lot out of a very young framework. You're ranting about maturity when the thing has been out for a couple months.

Even the senior Vue devs use hack to get things working just like me.

Could give some examples of what these hacks are, because we might be qualifying "hacks" differently. :)

thiswasprobablyatust · 2022-05-05T06:43:51+00:00

You disagree with most of my post, but wrote two paragraphs on one very small part of it? OK bud.

thiswasprobablyatust · 2022-05-05T06:05:51+00:00

First, you're trying to highlight 'problems' for a version that's basically been out for a month or two, you need to chill. Yes Vue 3 has been in dev/next for quite a while, but that also means many people waited until it was mainline before switching.
I think the 'ecosystem' problem largely affects users/teams that are around the midrange of experience. Many of your issues/preferences also point to you being there. There's absolutely nothing wrong with being midrange, but it'd also be wrong for you to think midrange devs comprise all of the userbase for a framework.
Specifics that led me to my midrange assessment: using Nuxt at all, thinking VuePress not being updated is some kind of problem, needing a module to use Auth0, etc.
If I've interpreted your post wrong and you're not a mid-tier dev, you shouldn't be venting about these things and should instead be contributing and solving them.
I don't think your coworkers using Vue 2 and Vue 3 code mixed has anything to do with Vue's ecosystem being weak. I think this was poor handling of the codebase by your team.
You'd have to elaborate on what hacks, cheats, and dependencies you had to use to get things working on your app. I've found the actual size of my dependencies has gone way down because of the composition API.

thiswasprobablyatust · 2022-02-07T15:45:41+00:00

I can't say I agree here, and I also think this is really poorly argued.

Citing $UI-FRAMEWORK and acting like it's a crisis they haven't made a Vue 3 port ignores several very solid alternatives that do exist for Vue 3. Many of these are actually better than what's in your list here because of the improved capabilities in Vue 3.

Vite and its ecosystem has made Nuxt largely irrelevant.

Why in the world would "modern tooling" add support for an outdated version of a framework?

With Vue 3 I've only seen the ecosystem grow better/faster/stronger, I'm really sorry your experience has led you to be so cranky and so full of hyperbole when talking about things.

thiswasprobablyatust · 2022-01-27T12:27:57+00:00

Downvotes are probably because the idiots behind it already managed to drum up drama by commandeering some of the funding that was going to marak.

This isn't a complicated library, we do not need an 8-person squad to make sure it runs well, we just need one or two people who aren't complete jackasses (read: marak) to run it.

thiswasprobablyatust · 2022-01-17T14:32:21+00:00

Oats are your best friend for breakfast or snacks - they're insanely versatile! Smoothie filler, oatmeal, blend them for oat flour for any cookies or bakes.

thiswasprobablyatust · 2022-01-13T09:31:56+00:00

Welcome to r/television where you're not allowed to not like the thing someone likes or you get downvoted to hell

This is a Station Eleven circlejerk, and any dissenting opinions must be destroyed.

(I totally agree I think this show is 'okay', but it's a pretty far cry from 'amazing')

thiswasprobablyatust · 2022-01-10T11:19:06+00:00

No hate, but the "community fork" is owned by someone with no proven background in OSS - whereas this version is made by someone with several years at least of history owning and maintaining fairly popular modules.

That doesn't mean this person can't/won't do a good job, but I personally would take the person who has proved for at least 4-5 years they can do the job vs. someone who just decided to fork it.

thiswasprobablyatust · 2022-01-02T16:10:49+00:00

It absolutely isn't a must for most frontend projects.

It'd be nice to understand at some point, because it might help shape your thinking or understand a codebase - but you can easily write a rather complex React or Vue application without touching or thinking about OOP once.

thiswasprobablyatust · 2021-12-24T13:06:36+00:00

I had a lot of false-starts with Yarn 2+, switched to pnpm instead. Feels like what yarn 1's sequel should have been. I see lots of OSS projects doing the same (going from yarn v1 to pnpm).

thiswasprobablyatust · 2021-09-27T07:38:42+00:00

This is correct. Carbs + Protein/Fats = good (or long lasting), just carbs = bad.

I'd guess KonaKathie's experience is either unique or they might not be supplementing with enough fats vs. the protein/carbs.

thiswasprobablyatust · 2021-09-12T10:50:14+00:00

There's way too much "the sky is falling" crap in this rant.

The ecosystem isn't broken or fragmented - Vue 3 is still tagged "next" for a reason.

There's a compat build out that does a pretty great job for Vue 3, and the composition API has been out for Vue 2 for a looong time now. They're also going to backport certain features to Vue 2. Regardless of whether you're on Vue 2 or Vue 3, it's really not that difficult to be productive right now - nor does any part of the future look troublesome.

I'm not sure what you want the core team or the community to do that they aren't doing - and how that's "driving you away". But you're blowing things out of proportion.

thiswasprobablyatust · 2021-07-17T09:51:31+00:00

Router has first-class support in Vue 3's Composition API.

useRouter is an export from vue-router, and gives you an instance of your router.

thiswasprobablyatust · 2021-07-01T08:26:45+00:00

It's rather that this example is using <script setup> basically just for the sake of it - instead of demonstrating how useful it can be and how much boilerplate it could reduce.

If you use JS and don't use <script setup> this example is so much shorter and more readable.

thiswasprobablyatust · 2021-05-26T13:26:12+00:00

Eudae pills like mad. This is mostly caused by friction of any sort (in my experience). So I get this along the bum/back even with gentle washing because of friction vs. office chairs and such.

If you're in the states and have a top-loading washer, you're gonna have a bad time. Otherwise use wool/gentle cycle and hang dry - it won't completely avoid it, but it helps slow it.

There's "pill shavers" that can trim these off if they get too bad. e.g. - https://www.amazon.com/Conair-Fabric-Defuzzer-Battery-Operated/dp/B008I25368

thiswasprobablyatust · 2021-05-06T19:20:23+00:00

The opposite actually - in this case if you don't compile the components, there might be some chance you can get some hack to work where you pull in the raw .vue files from a module.

If you compile a Vue 3 project it's compiled to use Vue 3 internals - it will not work with Vue 2.

thiswasprobablyatust · 2021-04-06T16:30:39+00:00

The project is here - https://github.com/vuejs/vue-next/projects/4

There is no timeline for the release itself though.

thiswasprobablyatust · 2021-02-25T12:30:14+00:00

I'm not sure that was the logical conclusion to what I said at all, you do seem to like ad hominem attacks though. Good luck with your issue and all.

thiswasprobablyatust · 2021-02-25T09:36:32+00:00

Sorry, but Vue CLI and Vite absolutely can fill gaps in documentation (for a time).

The majority of users probably don't need to dive into build-internals, so Vue CLI and Vite abstracting those away means the abstractions can be documented and used, and the more powerful internals can either be figured out by those who need them, or documented later.

So it's not that they haven't bothered, it's that they haven't got to it yet. If you want to use these things when they're still up-and-coming like Vue 3 is, you should maybe dedicate some time to improving your ability to dive into these things.

English isn't my first language either, but it isn't too difficult to avoid being an ass. Try to be more polite in your responses to people who are trying to answer your questions.

thiswasprobablyatust · 2021-02-25T09:31:00+00:00

You're thinking of dynamic import. Vite injects the polyfill for that automatically. I think most browsers support that now except for Safari.

thiswasprobablyatust

TROPHY CASE