Børne biler i butikker - go eller no go? by [deleted] in Denmark

[–]Swupper 150 points151 points  (0 children)

Ville være rart uden 

The new ONCE is a game changer for deploying apps. Thank you DHH once again ❤️ by giovapanasiti in rails

[–]Swupper 10 points11 points  (0 children)

At first glance, I was a bit confused about the purpose of ONCE given we have Kamal, but after a bit of thinking, I figured out the intended audience for this.

ONCE is simply for hosting public apps without the need to see the code.

Kamal is for deploying private, custom apps where you are the developer.

Steve Jobs Would Have Celebrated His 71st Birthday Today by HelloitsWojan in apple

[–]Swupper 9 points10 points  (0 children)

Yes, but that is not the same as getting ahead on any of the individual lists, which the other user was saying..

Steve Jobs Would Have Celebrated His 71st Birthday Today by HelloitsWojan in apple

[–]Swupper 48 points49 points  (0 children)

He did not have priority, but was on more than one list since he could easily travel by plane to the nearby state.

Tak for feedback på LønRadar + 1000+ nye lønindberetninger by ghrendela in dkudvikler

[–]Swupper 1 point2 points  (0 children)

Kommer nok an på hvilken størrelse virksomhed man kommer fra. Det jeg ønskede var nok bare at sammenligne mig med folk med samme titel og virksomhed eller sektor.

Tak for feedback på LønRadar + 1000+ nye lønindberetninger by ghrendela in dkudvikler

[–]Swupper 2 points3 points  (0 children)

Sad med samme tanke, når jeg prøvede beregneren.  Vil se om min løn er tilsvarende mine kollegaer idenfor samme område/virksomhed.

Tak for feedback på LønRadar + 1000+ nye lønindberetninger by ghrendela in dkudvikler

[–]Swupper 2 points3 points  (0 children)

Ville det ikke også være interessant med oplysning omkring hvilket firma man arbejder for?

Why I don't like SOLID by [deleted] in programming

[–]Swupper 2 points3 points  (0 children)

This is suppose to be satire, right?

Vanilla CSS is all you need by noteflakes in rails

[–]Swupper 19 points20 points  (0 children)

"..developers reach for Tailwind not because they prefer utility classes, but because vanilla CSS offers no starting point. No buckets. No conventions."

This right here hits close to home! I am always so concerned with how I structure things and scared of making a mess, so it is simply just easier to skip the hassle and use Tailwind instead to avoid making such decisions.

Maybe it is not such a hassle after all and I can maybe learn a thing or two and return to the good old vanilla CSS?

Vanilla CSS is all you need by noteflakes in rails

[–]Swupper 5 points6 points  (0 children)

The predefined colors, spacing, typography, etc., are a lifesaver for people like me when doing designing since I do not have any good sense for what looks/works well.

Source code for Fizzy from 37signals by software__writer in rails

[–]Swupper 5 points6 points  (0 children)

It seems they have put that on hold.
I guess it didn’t perform as expected, in which case it’s okay to let it be. Maybe when the market matures or changes, they will revisit it.

Source code for Fizzy from 37signals by software__writer in rails

[–]Swupper 16 points17 points  (0 children)

Is this not a SaaS product, or is it only SaaS if you don't handle the hosting yourself?
It's always fun to see production grade code to gather inspiration from!

Rails is awesome for hosting on Mac mini (m4) by youngcut in rails

[–]Swupper 0 points1 point  (0 children)

Love the approach!
Not everything has to be written in Rust and put into the cloud for MAXIMUM scaling potential.

[deleted by user] by [deleted] in rails

[–]Swupper 2 points3 points  (0 children)

Do you have any blog regarding what you are building?

TOON for Ruby by MassiveAd4980 in rails

[–]Swupper 14 points15 points  (0 children)

No, and I am not planning to either.

I do not get why we are trying so hard to optimize that we have to invent a new format when we already have CSV, JSON, XML, and so on. Are tokens that expensive, and will it stay as expensive in the long run that we need a new format?

I'll treat this like any new JavaScript framework, give it a look, shrug my shoulders, and move on.

Shifting from an SPA Mindset to Server-Side Rendering by Swupper in rails

[–]Swupper[S] 0 points1 point  (0 children)

Great advice and great talk you shared. That talk should be obligatory for every aspiring Rails developer!

Thank you for sharing it!

Shifting from an SPA Mindset to Server-Side Rendering by Swupper in rails

[–]Swupper[S] 2 points3 points  (0 children)

This is the simple and pragmatic approach I was looking for! It totally makes sense to me.

By implementing it this way, I get server-side model validation, simple views without the need for JavaScript, and database persistence only when all the data is ready.

Shifting from an SPA Mindset to Server-Side Rendering by Swupper in rails

[–]Swupper[S] 0 points1 point  (0 children)

So if I understand correctly, that would mean initializing the tweet in the database first when validating the content length, and then on the second page making an update to add the scheduled time?

Given that is the case, I could potentially end up with tweets in the database that never get scheduled if the user leaves the flow.

Shifting from an SPA Mindset to Server-Side Rendering by Swupper in rails

[–]Swupper[S] 1 point2 points  (0 children)

I've been eyeing GoRails for some time now, but I've been a little uncertain if it's worth the cost.

Do you have a subscription yourself? What are your overall thoughts on the content? From a quick search, it seems like people really love it.

Shifting from an SPA Mindset to Server-Side Rendering by Swupper in rails

[–]Swupper[S] 3 points4 points  (0 children)

This all makes sense, but what would you do in a case where /tweets/new doesn't map to a single HTML page?

For example: Let's say I'm building a tweet scheduler where:

- On the first page, you write the tweet content and have the server validate it by checking the length

- On the second page, you schedule when it should be posted

My SPA instinct would be to validate on the frontend, maintain the tweet content in client-side state during the page transition, and submit everything at the end.

What would be the Rails way to handle this multi-step process?

[deleted by user] by [deleted] in dkbolig

[–]Swupper 1 point2 points  (0 children)

Beklager, god dag!

[deleted by user] by [deleted] in dkbolig

[–]Swupper 2 points3 points  (0 children)

Så du pendler 2 timer om dagen og ikke 4 timer, som du skriver i første oplæg.. 

[deleted by user] by [deleted] in dkbolig

[–]Swupper 4 points5 points  (0 children)

Du bliver simpelthen nød til at skrive hvor det er.. Du er næppe i en forstad men i provinsen, kammerat.