yoava

ADRs are similar, yet the important point is not the format of the design log entry, but it's usage with AI.

with design log, we ask the AI to create the ADR or log entry, but unlike ADR we 1. require the AI to ask question and we answer. 2. require the AI to update the design log after implementation with any drift from the original design.

Both of the above help to make the AI more precise and prevent context drift.

So right...

We have seen in one of our products a huge difference between saying

1. You are limited to 3000 units, then you can buy more. 2. You get 3000 units for free.

Guess which one was better...

Super cool. looks like a really fun project, and made me look at APL itself. Thanks for that.

I do have a question for you - do you see any real use case for APL today? Do you see ideas we can learn from APL?

I have to say, this made my smile.

I wander, what is the source of the idea? Are you using it in your team?

it is not that simple. If you are using JS generated sidenotes, they are invisible for SEO engines.

looks like a really deep analysis of side notes in web design. Super interesting.

However, I do not see a discussion of side notes and SEO (search engine optimization), and the implication of using this or that technique on SEO

nice idea.

Personally, I do not see myself using it, yet I can see the value and innovative line of thought.

good points.

Just keep in mind that it all started with the "Start" button in Windows 95, which kind of solves the same problems.

I wander, which is better?

cannot read, you are using medium which is not free

Having taken part in building the Wix microservices architecture, I have to say that I understand and accept the critique of the article. Microservices is not a magic architecture, it solves some problems with the price of others.

When we stared Wix, we stared as a monolith - at 2006. In 2008 we split this monolith into two services due to different SLA - building websites and serving websites.

In 2011 we stared splitting the monoliths into micro services to solve software delivery pipeline - ability to move fast and scale with number of developers. Today we have about 20,000 deployments of new software every year, with over 1000 developers.

At Wix we are constantly investing a lot to maintain the microservices architecture and make it productive for our developers. We are making tools and utilities to return DRY into microservices architecture (think CDC support, GDPR support, Monitoring support, Scaling, Access Control, etc.).

My takeaways -

* Microservices do not come for free. You have to invest in making it work for you

* When building a startup - build a monolith. Break it down later when you understand what you need.

* We as an industry do not understand how to build micro services. There are a lot of fundamental aspects of microservices that are not commonly known / understood or ready as of the shelf solutions.

VB and Delphi reference architecture was 2 tier - client and database. With this reference architecture, you are right about the security and distribution problems. You just reminded me of the shareware market and the hacked shareware markets...

However, early on, around 1998, people started talking on 3 tier architecture of client - server - database on both platforms. There where even attempts to build web pages using both platforms (and later on .Net), which failed because of a lot of reasons, one big reason was not understanding the advantages of CSS.

Having worked for 10 years on both Delphi and VS, I understand the experience you are talking about. Having the ability to draw UI is amazing, and super productive. For business applications, it is amazing.

However, I still remember at around 2002 that we where asked to build specific custom user experiences, I think it was around reports, and using VB or Delphi was a lot of programming using draw commands... while using HTML and CSS it was fairly easy, even with the browser differences of CSS.

Any custom component in VS or Delphi (I am talking atomic components, not composite) requires using basic draw commands, and a lot of them.

The end result was that both platforms are not as expressive in terms of UI as the web, you cannot compare basic draw commands to structured CSS.

in one word - CSS.

CSS has killed VB.

How? when you need to build any application with custom graphics or UX, in VB you are gonna writes tons of lines of code, while using CSS you just write 2-3 declarations.

I do not think the problem with VB was the language. I think it was the graphic / UI expressive power, a simple way to add and create custom components.

At the same time that both VB and Delphi reached peak usage, the web started to show how easy it is to express graphically and UI using CSS. When you have to write tons of lines of code in VB to get to the same as 3 lines of CSS...

Visual Basic died because of the Web.

VS, and Delphi, are the masters of creating desktop applications. However, both failed to port to the web, and them to mobile.

There are a lot of reasons why they failed -

* missing graphical expression capabilities for customer facing websites

* using languages that are not native JS, preventing them from utilizing the JS eco-system

* Vendors (Google, Apple) who for their own reasons kept mobile development native on their language and tools. And many more reasons.

Last, both have paved the way for low code application builders for enterprises, which are mostly aimed at internal systems (not customer facing).

Worth noting that we, at Wix, have built the Wix dev platform learning from VB and Delphi, creating a website builder platform with similar concepts (I am the creator of Velo by Wix, the Wix dev platform, and having 10 years experience programming VB and Delphi).

I agree. Web Designers and Developers will always be needed for the more unique look and feel, more unique animations and specific functionality.

I think the role of AI generated site is to help getting a better result fast, both for non professionals, but also for professionals as a starting point.

To be honest, for me it feels on the edge of being a scam...

Almost like buying what are clearly branded domains only to sell them later to brand owner...

(and keep in mind, I work for Wix)

website personalization is a huge evolving market, which at the moment only works for super large ecomm sites with large and well trained marketing teams.

It makes a lot of sense that we will see disruption in this area using some AI powered stuff.

Yes, I am.

I have stated this before, and do not hide it.

I do try to give honest replies, not marketing bull**t, sharing what I can when I can.

I do not think AI will replace the hard working folks of the web dev "industry". At least, not those who will evolve with AI.

AI can get you so much.

This "so much with AI" is a lot, and great for many websites.

This "so much with AI" is a great starting point for many other websites.

I believe professional (like you?) will be using AI based tools to automate the simple tasks and focus more on the added value only they can provide.

I believe those agencies that create the "so called cheap websites" will utilize such AI based tools to create better websites, faster, and more cost effective for their customers.

Given a talk like -

Agency: What is your budget?

Client: 500$

Agency (yesterday): I can only do so much

Agency (today): I can offer you more for the same budget

Almost - This tool helps select a template, adding business applications and creating default content. But then, you have the Wix drag & drop builder to continue customizing the website, adding animations, changing content, adding or removing pages / sections, changing design, etc.

The strength of this offering is that it is seamless with the experience Wix is based on.

Actually, Wix can do quite a bit more with AI ...

1. AI Text Creator 2. AI Template Text Creator 3. Alternative Layouts 4. AI Image Creator 5. Auto Background Removal and Auto Enhance 6. Auto-Generated Trailer 7. Product Descriptions 8. Product Recommendations 9. AI Domain Generator more coming soon...

see examples here https://www.wix.com/blog/avishai-abrahami-thoughts-about-ai#...

Well, it is only about Text as long as you consider as Text the following...

1. Image Creator 2. Alternative Layouts 3. Auto Background Removal and Auto Enhance 4. Auto-Generated Trailer

You can see full examples of each here https://www.wix.com/blog/avishai-abrahami-thoughts-about-ai#...

I think you get it wrong - this will actually improve the internet.

Most of the websites are created from Templates that are then updated to some degree with content and images.

A tool like this one makes the website starting point more unique, allowing the site owner to create a better website will less effort --> better quality websites

This is why Wix has taken the time with releasing an AI website builder - making sure it actually works

I think it will improve the internet by adding more diversity.

The reality is that most websites are built from templates using the template content and images as a base. Given AI generation, the "template" starting point turns into something unique, more tailored for the needs of the site owner.

At the same time, it can help you become more productive when building for your clients. At least as a base generation that you as an expert website builder can then improve by adding your specific added value

Velo runs only JavaScript, but unlike cloudflare, velo runs a full node.js.

With that in mind, you can a lot of things, from accessing your database or any other asset on aws (or gcp or azure). You can also use other wix apis, like payment api or the wix data database.

With node.js, the cold start problem is caused by how node loads files. For each file it does about 10 IO operations (to resolve the file from the module name), then load, parse and compile the file.

If using any file system that is not super fast, this amounts to long delays.

There are ways to get around that, but those are not available on lambda