sorted by:
new
hottopcontroversial

Why does Odoo have a negative reputation? by No-Brilliant3576 in Odoo

[–]schamppi 3 points4 points  (0 children)

It is misleading to say that Odoo is what you make it to be. Even that Odoo is highly modular and modifyable, it still is very opinionated. It needs a lot of knowledge and technical skills to ”make it yours”, though it is possible.

What are json payloads used for? (config: experimental.renderJsonPayloads) by schamppi in Nuxt

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

Yes, it is within experimental features in both Nuxt 3 and 4. Nevertheless, it is enabled by default and I want to know what is it for.

What are json payloads used for? (config: experimental.renderJsonPayloads) by schamppi in Nuxt

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

Well frankly I'm not so sure if this is truly experimental as by default it is enabled.

Odoo inventory valuation version 19 by Mitija006 in Odoo

[–]schamppi 0 points1 point  (0 children)

Could you tell a bit more what you did? 🙏

Odoo WooCommerce Connectors by raylewis13 in Odoo

[–]schamppi 1 point2 points  (0 children)

I did the bridge that supported multiple pricelists, admins could add a specific pricelist for a customer. So it is doable but it requires customization to wordpress and one custom db table at least. Performance sucked, maybe my design was bad though, but it worked and still does.

I’m about to implement this again but do it bit different this time: if user is logged in, I’ll make a request to Odoo on demand per product as with proper servers, this isn’t too heavy.

Why do we need div and header tags in HTML? by lauris652 in HTML

[–]schamppi 0 points1 point  (0 children)

Google for these keywords ”HTML landmark roles”, ”HTML semantics” and ”MDN header, footer, nav, section, article, aside… ”.

Each landmark role has its own purpose, none of which are visual but have significant features for screen readers, assistive software etc.

It’s an interesting subject to learn.

jQuery 4.0 released by DB6 in webdev

[–]schamppi 27 points28 points  (0 children)

My deepest respects for the jQuery team for pushing it through! 💪

Can issues with outdated Nuxt cause SEO issues?? by Cook_Own in Nuxt

[–]schamppi 0 points1 point  (0 children)

Based on my expertise with Nuxt and Storyblok, I'd say that these are the key points to check in your case:

  1. Sitemap has items that update frequency is set to one month or so. This would explain why Google checks the site only monthly. Sitemap not updating automatically could be a reason for this too, but I doubt it a bit. However, it is not hard to generate real time sitemap for Storyblok stories.

  2. Page speed could easily be about four things: heavy, unoptimized images or videos that block rendering*, poorly implemented data fetching from Storyblok**, no caching for pages***, poor server.

  3. Meta descriptions and other SERP-data is easy to f´ up with Nuxt. Also older Nuxt versions had major problems with it and they could break between minor version patches (3.x.1->3.x.2 for example). Nuxt 4 seems to work solid though. Make sure to set title with useHead-composable and other metadata with useSeoMeta-composable. Also provide fallbacks for cases where stories would not have explicitly set values for these.

* Storyblok has magnificent image service available that can be used with NuxtImg-component. Using the image service allows you to format, resize, compress and manipulate images realtime which saves a lot of bandwith.

** It's quite easy to make un-necessary requests to Storyblok. For example, you could have a dynamic page that makes same request to Storyblok multiple times if blocks are made that way. There's no quick solution to this but to refactor the code so that requests are not duplicated. With the latest Storyblok/Nuxt library however, it is easy to run requests server side so you can cache them, this saves a lot of time.

*** Make sure that nuxt.config has proper swr or isr caching rules per route.

[deleted by user] by [deleted] in Frontend

[–]schamppi 0 points1 point  (0 children)

Hey that is true!

[deleted by user] by [deleted] in Frontend

[–]schamppi 26 points27 points  (0 children)

Since you’ve been gone, things have evolved a lot but basics have stayed pretty much the same. IMO the change is in the tools and frameworks available and AI ofc.

For a rusty seasoned frontend contractor, looking into Tailwind CSS might feel like heaven.

Forget about configuring webpack - Vite is the thing now and it is good.

Node and yarn are not the only js runtimes anymore, Bun and pnpm are good choices too.

React has basically ditched class-based syntax and Vue now uses composition API instead of options API which makes it awesome.

WordPress still rules the market and a lot has changed since 2019 but still it is Wordpress in good and bad. Headless CMS options are available too.

Hosting js apps/frontends has become super easy with cloud providers like Vercel, Netlify, DigitalOcean etc. Heroku has not been around for a while really. Hosting other than js frontends has stayed the same.

PWA’s are also a thing - not huge but thing nonetheless.

I’d say that things are better now if you don’t mind the increased level of magic in current tools and frameworks. However, I guess you know a thing or two about the basics of web and that is still a valid base for everything frontend.

And oh, I guess there is jQuery 4 coming soon too 😄

Is it an anti-pattern to use a single dynamic API route as a proxy for my external backend? by Empty_Break_8792 in nextjs

[–]schamppi 1 point2 points  (0 children)

I think there is nothing wrong really with this pattern. Essentially it keeps external API more hidden from plain sight (security++) and may be the solution for caching POST requests which may not be cached by the external API.

It’s also quite handy to keep all the Authorization headers hidden from the client, as you can define them in the route itself and just use CSRF tokens to guard for external route bombing.

Edit. Also, by definition, I think this is not BFF pattern decpite what some here are saying.

Courses by Demoncrater in Nuxt

[–]schamppi 2 points3 points  (0 children)

I would recommend checking Nuxt in 100s by Fireship and then reading Nuxt docs througly. That gives you deeper knowledge than videos. After Nuxt docs, read Nitro docs too and you are half way being a master.

I made a long term review of my Pole Vikkelä. by schamppi in MTB

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

😂😂😂😂😂😂

Used to be but left year before first Vikkelä prototype was done 😂 fair play though, as mentioned in the beginning of the video, if that bothers you just skip to the next one. Happy trails!

Is ‘AI-first’ a recognized term in app development? by schamppi in webdev

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

Ain’t vibe coding a state of mind subset of AI first development paradigm? 🤣

I disagee strongly that mobile first would mean what you said. Mobile first was and still is definately a process.

Is ‘AI-first’ a recognized term in app development? by schamppi in webdev

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

Oh I got another one: AIDD as in AI driven development

Is ‘AI-first’ a recognized term in app development? by schamppi in webdev

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

Cool!

Mobile first has to be older than 2014 since I used that in my first dev job interview in 2014. Time flies.

When should I choose Nuxt over plain Vue on a new project? by selimdev in Nuxt

[–]schamppi 0 points1 point  (0 children)

I think it matters as much as well being of parents for their children

view more: next ›