I have to know .. any chance the name was inspired by Alan Kay? :]
Show HN: Alan – a low-code application platform
51–60 of 178 posts
Re: Show HN: Alan – a low-code application platform
#52Earlier quoted context omitted.
I believe it is a head with a shirt collar. But at first glance, I thought it was a beer mug.
I'm disconcerted after reading this thread, seeing that some people somehow think that "low code" means "low-level code" (really?) and mistaking a collared shirt for legs. I'm going to assume it's because this post was made early in the morning and no one has had their coffee yet.
Re: Show HN: Alan – a low-code application platform
#53Re: Show HN: Alan – a low-code application platform
#54How do you compare yourself against other "low code" platforms in the 4GL landscape? https://en.wikipedia.org/wiki/Fourth-generation_programming_...
I would also like to see this comparison. Another thing is; HN is really the wrong audience for this. Technologists here will spin up a vm/container with their stack of choice. Indeed; ruby and rails, django, node, all fill the void 4GLs did decades ago. Finding and reaching users for this type of tool is the challenge imo. Implementation is the easy part.
Re: Show HN: Alan – a low-code application platform
#55Any thoughts on pricing model yet? I see it's free for personal use. Who do you view as your competition?
We're still feeling out the market here, to see where we can take it. It will probably stay free for personal use and then grow from there with services like hosting, etc. Pricing model for businesses is something we're looking at from case to case currently. Competitors include Mendix, Outsystems etc., when it comes to low-code and serving citizen developers. Excel as well. On the other hand there are still a lot of…
Re: Show HN: Alan – a low-code application platform
#56Re: Show HN: Alan – a low-code application platform
#57How do you compare yourself against other "low code" platforms in the 4GL landscape? https://en.wikipedia.org/wiki/Fourth-generation_programming_...
Alan plays a longer game, with a drastically different approach to specification and development of applications of any level of complexity. Models drive everything and you can't look "under the hood" to look at or modify the implementation. Even at the level of the platform itself, models and code generation drive down the amount of 3GL code we have to deal with. WYSIWYG editors and drag-and-drop UI builders aren't a starting point, it's something we might grow towards supporting in the future.
Re: Show HN: Alan – a low-code application platform
#58Re: Show HN: Alan – a low-code application platform
#59How do you take this from here to the next step? Let's say I want to develop a multi user todo and I've followed the examples and now have some Users who log in entering a password. Someone points out that I shouldn't be storing passwords in plain text so I want to store them hashed. Despite there being hints in the documentation that this is possible (migrations shows the password hashed), it's not clear how to carr…
Well, in this particular case passwords are always hashed. So the platform deals with that for you. Other changes to the data model need a migration, which is covered here: https://alan-platform.com/pages/tuts/migration.html
/* 'Users': collection { 'Password': text }*/
How does the platform know to hash that? Is it looking for magic property names?
Re: Show HN: Alan – a low-code application platform
#60 'Week Day': stategroup (
'Monday' -> { }
'Tuesday' -> { }
'Wednesday' -> { }
'Thursday' -> { }
'Friday' -> { }
'Saturday' -> { }
'Sunday' -> { }
)
I think it would be nice if you could just write something like: 'Week Day': stategroup ('Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday', 'Sunday')
Or even something like %w() from Ruby: 'Week Day': stategroup %w(Monday Tuesday Wednesday Thursday Friday Saturday Sunday)
I also see a lot of "'Yes' -> { }" and "'No' -> { }" stategroups that are quite verbose. So it would be nice if you could just do: 'Active': stategroup @default: 'Yes' %w(Yes No)
'Subsidized': stategroup @default: 'Yes' %w(Yes No)
Or even a "Boolean" shorthand instead of 'Yes' and 'No': 'Active': stategroup @default: 'Yes' Boolean
'Subsidized': stategroup @default: 'Yes' Boolean
Also 'can-create:' and 'can-update:' seem to always have some shared logic. Instead of: can-create: user +'Roles'?'Manager'|'Yes'
|| user +'Roles'?'Project Manager'|'Yes'
can-update: user +'Roles'?'Manager'|'Yes'
|| user +'Roles'?'Project Manager'|'Yes'
|| equal ( user , $ >'Project Group'>'Owner'>key )
You could do something like: can-create: user +'Roles'?'Manager'|'Yes'
|| user +'Roles'?'Project Manager'|'Yes'
can-update: &can-create || equal ( user , $ >'Project Group'>'Owner'>key )
[0] https://github.com/M-industries/Hours/blob/master/interfaces...