awayto VS concise-encoding

Hey folks, just putting this up as a demo link for people to try out. It's a project I've been working on since January and in light of recent framework posts lately I figured I'd start talking about my own.

The link is a demo site of Awayto v2 [1] (ignore the front page info that's all from version 1). Awayto [0] started out as a quick deploy app which grew to exist via AWS. I felt the need to make something that wasn't so closely tied to cloud infra, and Awayto v2 is that. Currently deployed on hetzner vms, using Tailscale for networking, there is a great deal of things going on. There is a local installation path planned, as long as you provide your own servers, etc, as it all just works on Tailscale anyway. I'm still working on docs, but the goal is to spit out _everything_ a dev might want to control in their stack. My current version of deploying to hetzner sets up 7 servers (2 ns, exit, build, app, db, svc). Git profile [2] for more info, tech stack info.

This is just a short demo and will only be up a limited time. There's no email validation or anything, gibberish is welcome. You are not being tracked. I know I need how-to docs, video assists, and all that. Slow and steady. It's being hosted from a single warehouse in the Pacific Northwest, be kind. Caching is in play and not perfectly tuned so maybe wait a few minutes if something doesn't automatically show up. Any feedback is awesome. Cheers!

[0] https://github.com/keybittech/awayto

This is really cool to see in this format. Over the last few years I have spent my free time crafting a framework under similar ideologies. I think a lot of web devs end up making similar tools throughout their career, but perhaps never get to the point of sharing what they make. I finally formalized my framework last year and am well into battle testing it with clients and different projects. https://awayto.dev

In a similar light to what this FWA group is presenting, I also have put forth some points about why this style of web dev architecture is important and effective. https://awayto.blog/posts/webapps/

Actually, I started out reading Million Dollar Consulting last year and one of the first chapters essentially talks about the importance of having a portfolio of work, and being able to capitalize off that body of knowledge within to grow more as a consultant. Well, I took that as a sign to formalize a framework that would allow me to do my development work in a much more effective manner, as well as provide more out of the box functionality for my clients.

Overall, the experience has been really positive. Obviously I don't get to use my own framework with every client, and that's a good thing. But, when working with clients who need basic business problems solved, having an FWA style framework is going to allow you to iterate so much faster than traditional MVC platforms. At least this has been my experience. Specifically to that point, with templated and loosely coupled parts, you don't have to spend too long building your web app to get it to do something exceptional.

Location: Pacific Northwest

Remote: Yes

Willing to relocate: For Contract or Consulting Only

Technologies: Java, C#, Javascript, Typescript, HTML, CSS, React, Redux, Material UI, NodeJS, Webpack, Postgres, Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, HITRUST, FERPA

Résumé/CV: https://www.linkedin.com/in/joe-mccormick-76224429/

Email: [email protected]

My name is Joe. If you are looking for a consulting- or contract-based resource, I am interested and open to take on projects of many varieties. Over the last 10 years, my professional experience has touched on Education, Professional Consulting, IT Management, E-Commerce, and I hold my MA in English teaching. I have helmed numerous, extremely successful software development teams within the companies I have worked at, on projects of large complexity, some with millions of users and in revenue.

Check out https://awayto.dev which is a free open source web application platform. It uses React, Redux, Material UI, NodeJS, Typescript, Webpack, Postgres, Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, as well as my own custom scripts. Awayto makes it fast to deploy low-cost web applications and then have a skilled developer come in and build up your application.

Thank you for your time.

SEEKING WORK - Pacific Northwest - Contract/Consulting Remote/Onsite

If you are looking for a consulting- or contract-based resource, I am interested and open to take on projects of many varieties. Over the last 10 years, my professional experience has touched on Education, Professional Consulting, IT Management, E-Commerce, and I hold my MA in English teaching. I have led multiple successful development teams within the companies I have worked at, on projects of large complexity, some with millions of users and in revenue.

For my most recent completed work, I created https://awayto.dev, a free open source web application generation platform. It uses React, Redux, Material UI, NodeJS, Typescript, Webpack, Postgres, AWS Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, as well as my own custom scripts. Awayto makes it fast to deploy low-cost web applications and then have a skilled developer come in and build up your application. https://github.com/keybittech/awayto

Thank you for your time.

Javascript, Typescript, Java, C#, HTML, CSS, HITRUST, FERPA

Inquiries: [email protected] Website: https://awayto.dev LinkedIn: https://www.linkedin.com/in/joe-mccormick-76224429/

Willing to relocate: For Contract or Consulting Only

Technologies: Java, C#, Javascript, Typescript, HTML, CSS, React, Redux, Material UI, NodeJS, Webpack, Postgres, Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, HITRUST, FERPA

Résumé/CV: https://www.linkedin.com/in/joe-mccormick-76224429/

Email: [email protected]

If you are looking for a consulting- or contract-based resource, I am interested and open to take on projects of many varieties. Over the last 10 years, my professional experience has touched on Education, Professional Consulting, IT Management, E-Commerce, and I hold my MA in English teaching. I have led multiple successful development teams within the companies I have worked at, on projects of large complexity, some with millions of users and in revenue.

For my most recent completed work, I created https://awayto.dev, a free open source web application generation platform. It uses React, Redux, Material UI, NodeJS, Typescript, Webpack, Postgres, AWS Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, as well as my own custom scripts. Awayto makes it fast to deploy low-cost web applications and then have a skilled developer come in and build up your application. https://github.com/keybittech/awayto

Thank you for your time.

I made a web application generation tool built on top of AWS. It deploys all the basics you need for a web application in the modern era (db, ui, api, users, groups, roles).

https://awayto.dev -- Check out the video

https://github.com/keybittech/awayto

If you like making tools for developers, contractors, and the business world. Come check us out and join the discord!

Hey there, I work on a project called Awayto. It generates and deploys web applications to AWS with all the base line bells and whistles (db, api, ui, user mgmt, react, typescript). I enjoy working on tools for developers and this is a project that's supposed to help developer consultants. It's a full stack framework, and there are of course many ways you could help or be involved, so if it sounds interesting please check it out!

https://github.com/keybittech/awayto

https://awayto.dev

A lot of the comments here are about difficulty cloud tech navigation/adoption. I create a framework built on top of AWS to try to alleviate a great deal of the infra management aspects of running web applications. It sets you up with all the basics out of the box in about 10 minutes (db, api, ui, users, groups, roles).

https://awayto.dev

https://github.com/keybittech/awayto

Along the same vein as other posts in this thread, startups and contractors need instantaneous test bed environments that support a lot out of the gate, and which can be the basis to scale from. I've been a contractor off and on for a few years and have seen this need first hand. So my tool is meant to fill in the foundations of great ideas, so those ideas can grow faster. I think that's an essential trait of cloud services that you will be hard-pressed to find elsewhere.

SEEKING WORK - Pacific Northwest - Contract/Consulting Remote/Onsite

If you are looking for a consulting- or contract-based resource, I am interested and open to take on projects of many varieties. Over the last 10 years, my professional experience has touched on Education, Professional Consulting, IT Management, E-Commerce, and I hold my MA in English teaching. I have led multiple successful development teams within the companies I have worked at, on projects of large complexity, some with millions of users and in revenue.

As a side project, I created https://awayto.dev, a free open source web application generation platform. It uses React, Redux, Material UI, NodeJS, Typescript, Webpack, Postgres, AWS Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, as well as my own custom scripts. Awayto makes it fast to deploy low-cost web applications and then have a skilled developer come in and build up your application.

Thank you for your time.

Java, C#, Javascript, Typescript, HTML, CSS, PHP, Ruby, Python, HITRUST, FERPA

Inquiries: [email protected]

Remote: Yes

Willing to relocate: For Contract or Consulting Only

Technologies: Java, C#, Javascript, Typescript, HTML, CSS, React, Redux, Material UI, NodeJS, Webpack, Postgres, Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, HITRUST, FERPA

Résumé/CV: https://www.linkedin.com/in/joe-mccormick-76224429/

Email: [email protected]

If you are looking for a consulting- or contract-based resource, I am interested and open to take on projects of many varieties. Over the last 10 years, my professional experience has touched on Education, Professional Consulting, IT Management, E-Commerce, and I hold my MA in English teaching. I have led multiple successful development teams within the companies I have worked at, on projects of large complexity, some with millions of users and in revenue.

As a side project, I created https://awayto.dev, a free open source web application generation platform. It uses React, Redux, Material UI, NodeJS, Typescript, Webpack, Postgres, AWS Cognito, Lambda, CloudFormation, CloudFront, S3, API Gateway, as well as my own custom scripts. Awayto makes it fast to deploy low-cost web applications and then have a skilled developer come in and build up your application.

Thank you for your time.

"Local time" is time zone metadata. I've written a fair bit about timekeeping, because the context of what you're capturing becomes very important: https://github.com/kstenerud/concise-encoding/blob/master/ce...

This is basically why I ended up rolling my own text date format for Concise Encoding: https://github.com/kstenerud/concise-encoding/blob/master/ct...

ISO 8601 and RFC 3339 are fine for dates in the past, but they're not great as a general time format.

This looks similar to https://concise-encoding.org/

Dogma was developed as a consequence of trying to describe Concise Binary Encoding. The CBE spec used to look like the preserves binary spec, full of hex values, tables and various ad-hoc illustrations: https://preserves.dev/preserves-binary.html

Now the CBE formal description looks like this: https://github.com/kstenerud/concise-encoding/blob/master/cb...

And the regular documentation looks like this: https://github.com/kstenerud/concise-encoding/blob/master/cb...

Dogma also does text formats (Concise Encoding has a text and binary format, so I needed a metalanguage that could do both in order to make it less jarring for a reader):

https://github.com/kstenerud/concise-encoding/blob/master/ct...

https://github.com/kstenerud/concise-encoding/blob/master/ct...

Hey thanks for taking the time to critique!

I actually do have an ANTLR file that is about 90% of the way there ( https://github.com/kstenerud/concise-encoding/tree/master/an... ), so I could use those as a basis...

One thing I'm not sure about is how to define a BNF rule that says for example: "An identifier is a series of characters from unicode categories Cf, L, M, N, and these specific symbol characters". BNF feels very ASCII-centric...

It's still in the prerelease stage, but v1 will be released later this year. I'm mostly getting hits from China since they tend to be a lot more worried about security. I expect the rest of the world to catch on to the gaping security holes of JSON and friends in the next few years as the more sophisticated actors start taking advantage of them. For example https://github.com/kstenerud/concise-encoding/blob/master/ce...

There are still a few things to do:

- Update enctool (https://github.com/kstenerud/enctool) to integrate https://cuelang.org so that there's at least a command line schema validator for CE.

- Update the grammar file (https://github.com/kstenerud/concise-encoding/tree/master/an...) because it's a bit out of date.

- Revamp the compliance tests to be themselves written in Concise Encoding (for example https://github.com/kstenerud/go-concise-encoding/blob/master... but I'll be simplifying the format some more). That way, we can run the same tests on all CE implementations instead of everyone coming up with their own. I'll move the test definitions to their own repo when they're done and then you can just submodule it.

I'm thinking that they should look more like:

    c1

Ugh Unicode has been the bane of my existence trying to write a text format spec. I started by trying to forbid certain characters to keep files editable and avoid Unicode rendering exploits (like hiding text, or making structured text behave differently than it looks), but in the end it became so much like herding cats that I had to just settle on https://github.com/kstenerud/concise-encoding/blob/master/ct...

Basically allow everything except some separators, most control chars, and some lookalike characters (which have to be updated as more characters are added to Unicode). It's not as clean as I'd like, but it's at least manageable this way.

You might get a kick out of Concise Encoding then (shameless plug). It focuses on security and consistency of behavior.

https://concise-encoding.org/

In particular:

* How to deal with unrepresentable values: https://github.com/kstenerud/concise-encoding/blob/master/ce...

* Mandatory limits and security considerations: https://github.com/kstenerud/concise-encoding/blob/master/ce...

* Consistent error classification and processing: https://github.com/kstenerud/concise-encoding/blob/master/ce...

In the above example, `&a:` means mark the next object and give it symbolic identifier "a". `$a` means look up the reference to symbolic identifier "a". So this is a map whose "recusive link" key is a pointer to the map itself. How this data is represented internally by the receiver of such a document (a table, a struct, etc) is up to the implementation.

> - Time zones: ASN.1 supports ISO 8601 time types, including specification of local or UTC time.

Yes, this is the major failing of ISO 8601: They don't have true time zones. It only uses UTC offsets, which are a bad idea for so many reasons. https://github.com/kstenerud/concise-encoding/blob/master/ce...

> - Bin + txt: Again, I'm unclear on what you mean here, but ASN.1 has both binary and text-based encodings

Ah cool, didn't know about those.

> - Versioned: Also a little unclear to me

The intent is to specify the exact document formatting that the decoder can expect. For example we could in theory decide make CBE version 2 a bit-oriented format instead of byte-oriented in order to save space at the cost of processing time. It would be completely unreadable to a CBE 1 decoder, but since the document starts with 0x83 0x02 instead of 0x83 0x01, a CBE 1 decoder would say "I can't decode this" and a CBE 2 decoder would say "I can decode this".

With documents versioned to the spec, we can change even the fundamental structure of the format to deal with ANYTHING that might come up in future. Maybe a new security flaw in CBE 1 is discovered. Maybe a new data type becomes so popular that it would be crazy not to include it, etc. This avoids polluting the simpler encodings with deprecated types and bloating the format.