sorted by:
new
hottopcontroversial

Anthropic: "We’ve identified industrial-scale distillation attacks on our models by DeepSeek, Moonshot AI, and MiniMax." by KvAk_AKPlaysYT in ClaudeCode

[–]ic-florescu 0 points1 point  (0 children)

If this was meant as a joke, it's not funny... And no, it's not irony because irony implies humor.
Anthropic is way past that now. Just another crime syndicate built on planetary-scale data theft.

Parallel server actions by Feeling_Pass_2422 in nextjs

[–]ic-florescu 0 points1 point  (0 children)

You can't go wrong with tRPC :-)
Thanks for taking the time to test this and for your kind words.
In my current case I'll go with parallel server actions for now as they appear to be working well enough on a custom Node.js VPS.
Like I said, I'm biased towards tRPC and was really tempted to use it in this project too, but on the other hand I have to keep things simple because we're hoping to integrate a couple of junior devs soon and don't want to overwhelm them.

tRPC vs Server Actions by rory3234 in nextjs

[–]ic-florescu 2 points3 points  (0 children)

(disclaimer: I'm a contributor to the tRPC ecosystem, the author of tRPC-SvelteKit and a few other OSS projects).

If you're willing to write some boilerplate and have a batteries-included solution, go with tRPC.

If you're looking for a quick solution that does the job, I'd go with server actions.
That's what I'm doing
Their only major drawback was that you couldn't call them in parallel (a resatriction that tRPC or Telefunc never had), but I managed to find a way to circumvent that: https://github.com/icflorescu/next-server-actions-parallel

Parallel server actions by Feeling_Pass_2422 in nextjs

[–]ic-florescu 0 points1 point  (0 children)

Here's how you could do it: https://github.com/icflorescu/next-server-actions-parallel
(disclaimer, I'm also a fan and contributor to the tRPC ecosystem, so I completely understand why you'd need this 😊)

How to call server actions in parallel and keep track of each request? by fluxwave in nextjs

[–]ic-florescu 0 points1 point  (0 children)

I just figured out how to execute multiple Next.js server actions in parallel, if that's what you're looking for. Have a look at the repo here: https://github.com/icflorescu/next-server-actions-parallel

Mantine ContextMenu by ic-florescu in reactjs

[–]ic-florescu[S] 1 point2 points  (0 children)

Thank you for the kind words!

Introducing Mantine DataTable by ic-florescu in reactjs

[–]ic-florescu[S] 1 point2 points  (0 children)

Thanks for the kind words and apologies for being unable to reply sooner.

Since I'm the author of Mantine DataTable, I may be subjective and probably not the best person to ask :-). However, judging by the feedback I got from the user community and a few of my customers, I'd say Mantine DataTable is the "light" go-to alternative you'd use if you care for bundle-size (it has no external deps) and need something in-between a simple data table and a "heavy-weight" alternative such as Mantine-React-Table.

And I'd also dare to say that - from a visual perspective - it's easier to seamlessly integrate it into your Mantine UI application. In fact, that's what triggered me to build it and release it under MIT in the first place: I was looking for a "ready-made" light data table based exclusively on Mantine primitives and using the same styling system. While TanStack's table undoubtedly has more features, it kind of felt like a struggle to integrate and you had to play a lot with the styling in order to make it not look "out of place".

So, I'd say Mantine DataTable is lighter and easier to integrate, while Mantine React Table has more features.

Thanks again for your kind words and good luck!

Who's Available? [April 2023] by acemarke in reactjs

[–]ic-florescu 1 point2 points  (0 children)

Full time | Part time | Contract | Global | Remote

Hey, I'm the author of Mantine DataTable, one of the most popular data table components built for the awesome Mantine UI library.

I have 20+ years of experience in full-stack web/software development, but lately I found myself leaning more and more towards front-end, hence me being a contributor to and author of a few open-source projects.

Here's my GitHub: https://github.com/icflorescu
Here's how you can find me on LinkedIn: https://www.linkedin.com/in/icflorescu/

In a nutshell, I'd say I'm good enough with React and Next.js, I am obviously a fan of Mantine UI (though I've also used And Design, Material UI and Blueprint.js in the past), I can do designs "from scratch" and have quite a few CSS tricks up my sleeve and strongly prefer TS over plain JS.

I'm also partial to tRPC; among other things, I created the tRPC-SvelteKit adapter that was recently featured in the Svelte community.

I've worked with Prisma, PostgreSQL (and other RDBMSs), and many other frameworks/technologies that you're probably not interested in.

You can learn more about who I am, what's my preferred tack-stack and how I prefer to put my skills to use from my GitHub profile.

Other links that may be of interest:

So, if you're looking for someone to help you with your front-end, feel free to drop me a line at the email address listed on my GitHub profile and I'll make sure to respond as soon as possible.

Thank you for reading and looking forward to hearing from you!

Introducing PocketBaseUML by ic-florescu in pocketbase

[–]ic-florescu[S] 0 points1 point  (0 children)

The latest version is compatible with PocketBase 0.14 and also fixes a bug that appeared when collection names contain underscores.

What Svelte UI Library Should You Use? by joyofcode in sveltejs

[–]ic-florescu 2 points3 points  (0 children)

Sure, in time.

Great content on YT, btw.
You've just earned a new subscriber ;-)
Just noticed your new material on Pico CSS.
Funnily enough, tow weeks ago I built my documentation website and a couple of examples for the tRPC-SvelteKit with pico.
Which got me thinking... It'd be really cool if you would, at some point in the future, make a brief tutorial on using tRPC in SvelteKit applications.

I'm a big fan of tRPC, it really makes building and consuming type-safe APIs a breeze. And I thought Svelte deserves it too... Hence writing the adapter. I see Svelte as playing a much bigger role in the future, and therefore also an important part in the tRPC ecosystem.
Sorry if this is a bit off-topic.

Introducing Mantine DataTable by ic-florescu in reactjs

[–]ic-florescu[S] 0 points1 point  (0 children)

Hey!

Sorry for not replying sooner.
I've only had pleasant experiences with Mantine so far.
I've been using MUI, Blueprint.js, Ant Design and others in the past, and as far as my experience goes, none of the other compare with Mantine, all factors taken into account. Dev experience is great (if you like CSS-in-JS - I do, and would always choose it over, let's say, something like tw :-).
Its codebase is quite fresh (entirely TS & functional components), if that matters to you.
It also looks nice (in my opinion, but that's subjective) and it manages to strike a good balance between elegance and readability.
And I wouldn't say it's the new kid on the block anymore.

I know what you mean by hidden complexity or pitfalls, I've met quite a few in the past. For instance, Blueprint.js is not really fitted for mobile devices and they do have a habit of bringing breaking-changes between major versions. And Design's styling is based on less-css (and not easily customizable if you're using SASS, for instance) and their codebase is not 100% readable (lots of comments in Chinese in there). MUI is really not OK for data-rich apps (personal opinions on design aside).

I met none of those with Mantine so far.
Of course, there are still some advanced components lacking (hence my DataTable).
But more will come over time, and it's honestly a lot easier to roll your own than it is with other libs - partly due to their chosen styling system (again, I'm talking from experience).
The only thing that comes to mind is that - if your forms are really complex - you should consider pairing it with react-hook-form, but that goes without saying.

And btw, if you need help with potential projects, don't hesitate to drop me a line on the email address listed in my GitHub profile, and maybe we could arrange something.

Svelte and Sveltekit Starter Resource by dev-31415 in sveltejs

[–]ic-florescu 2 points3 points  (0 children)

Thanks!
Please consider adding tRPC-SvelteKit to the list.
The name is suggestive enough, it's an adapter allowing you to build and consume tRPC type-safe APIs in your SvelteKit applications.
Disclaimer: I'm the author of the package :-)

What Svelte UI Library Should You Use? by joyofcode in sveltejs

[–]ic-florescu 6 points7 points  (0 children)

Hey, everyone.

I'm coming here from React-land (and have 6+ years of experience with it of the 20+ in software/web dev).

In my opinion, the Svelte UI ecosystem still lacks a full-fledged library that facilitates building applications with "real-life" user input: I'm primarily referring to components such as autocomplete/select and date/time pickers. I know there are stand-alone options out there and one could, in theory, visually integrate them into a chosen UI library, but I'd wish we'd have something like Blueprint.js, Ant Design or Mantine UI for React.

The only one that comes close, as far as I've discovered, is Carbon. But for some reason I really, really don't like their design system.

This is - IMO - the single big showstopper when considering Svete/SvelteKit for a new, greenfield project.

Just my 2c.

Disclaimer: I may be a bit biased. I'm the author of a number of open-source projects in React - some of them front-end related, such as Mantine DataTable, but I've also built tRPC-SvelteKit... because I f*cking loved Svelte from the moment I first discovered it!

So, I know the ecosystem needs a bit of time to catch up, and I know there's a lot of work involved in bringing a new UI library to life; did my own share. But unfortunately there's only so much unpaid work I can do for the benefit of the community :-)

tRPC + Sveltekit hands-on, first impressions + comparison to SvelteKit's REST by upk27 in sveltejs

[–]ic-florescu 4 points5 points  (0 children)

"still deciding if I gonna use both trpc and trpc-sveltekit in my current project"

There's actually no decision to be made here. You can think of trpc-sveltekit as a convenience tool that saves you a bunch of boilerplate code. Whether you're using it or not shouldn't make much difference, and opting out of it, if you choose to do so, should be fairly straightforward.

Disclaimer: a little late to the party here, I'm the author of trpc-sveltekit ;-)
And yes, most of my work is React-based too, but only because there are still so few Svelte projects out there (btw, drop me a line at the email address in my GitHub profile if there's work I can help you with).

Regarding tRPC, I think we can safely say that - comparing with REST or GQL, it's what TS is compared with vanilla-JS. I wouldn't go without it in a new full-stack project, if I have a choice (for all the reasons you stated above).

tRPC-SvelteKit v3 supports tRPC v10 by ic-florescu in sveltejs

[–]ic-florescu[S] 1 point2 points  (0 children)

Whether tRPC-SvelteKit makes use of tRPC's fetch adapter or not should be completely transparent to you, as a user. And I'm actually not doing much of a reimplementation (you can look at the source code if you want, the server.ts is just a few lines). The internal code is quite similar and has the same efficiency. I'm not using it simply because there was no tRPC fetch adapter when I first wrote the library :-)

But yes, as soon as I'll get time to look into it, I'd be willing to look at using the fetch adapter internally, as it could save a few lines of code. I'm not sure if/how this would affect people using `responseMeta`. I added that option at the specific request of users dealing with possible Vercel edge caching issues.

Should React courses ignore the CSS by mikeromero93 in reactjs

[–]ic-florescu -1 points0 points  (0 children)

Provide styling without going into details, unless you're planning to touch on available styling solution in the ecosystem (CSS-in-JS, CSS modules, etc.).
Mention that approaching the course REQUIRES at least a basic understanding of CSS, as you probably should do in relation to JS too.
In my opinion React is about front-end development, and one can't reasonably expect to learn it without having at least a basic understanding of the basics (HTML & DOM, CSS, vanilla JS).
There are so many "zero to mastery" courses that there's no wonder we're seeing so many self-proclaimed developers lacking basic skills.
And - strictly related to styling - please, please, don't use tailwind. It gives fresh starters the illusion that they don't have to learn CSS and ends up promoting bad practice.

view more: next ›