cettox
Joined 13 years ago
Karma
8
Submissions
24
Member since
May 3
Recent submissions
Comment · 2 years ago
Comment · 2 years ago
Location: Turkey
Remote: only option (international travel every 2-3 months is possible)
Schedule a chat: https://calendly.com/gkemaldag/interview-with-kemal
Willing to relocate: No
Technologies: Kubernetes, GCP, Node.js, React.js, Terraform
Linked.in: https://www.linkedin.com/in/kemaldagdotjs/
email: [email protected]
I'm a math graduate, self-taught myself programming. I'm in the web development business for over 13 years. I've been working in every part of the stack, but last 6 years is focused heavily on SRE/Platform Engineering/DevOps related work.
Comment · 3 years ago
Hi all, my name is Kemal Dag. I have 12 years of professional experience from frontend, backend to the deepest of the stack: DevOps/SRE. Currently I am open for a new role.
Location:Turkey Remote:Only remote Willing to relocate: no Technologies: node.js, react, mongodb, mysql, GCP, Terraform, Kubernetes Résumé/CV:https://www.linkedin.com/in/kemaldagdotjs Email: [email protected]
Comment · 4 years ago
Sorry for the trouble, that is fixed
Comment · 11 years ago
I agree, it is almost ignored in most tutorials and I only see implementation examples in some neat projects, and always left with a wondering mind.
Comment · 12 years ago
I wonder why they disabled it after enabling for a very short time.
Comment · 12 years ago
"asta la vista baby" query does not result with Terminator at all!
Comment · 12 years ago
As many pointed that out using Pidgeon Hole principle, it is not practical to create a compression index(A lookup index where you map actual data with some kind of adresses preferably smaller than sequences), using every possible n byte sequence of your data!
Because your index size would be at least equal or higher than your original data.
The only way you get a smaller compression index, you have to look for recurrences, and try to only include most recurring sequences up to a number(there would be a tradeof and an optimal number for compression ratio) and left other sequences uncompressed. Only this way you can achieve compression ratio's smaller than 100%.
Comment · 12 years ago
Sorry, I can confirm it is 8kb gzipped, and it is acceptable. I may seemed over reacting to this because I am a developer who spent last month optimizing web pages by reducing js size :)
How we achieve lightweightness? Currently our only sin is, our inclusion of jquery, that is just to have some cross browser way of interacting with DOM, then we hand craft required JS code based on features used in the form builder. We then ship a lightweight runtime, whose whole purpose is to load necessary JS code pieces to have a functional form that is lightning fast. Ps: we havent gone to the last mile in optimizations, but we definteley will. Even with current state, it is the most lightweight form builder out there.
It is open source, MIT licensed, built on modern stack(react, node.js, Kubernetes and Google Cloud) and we are also hosting a freemium version.
I think, there will be ever increasing need and market for lightweight products, as modern IT means a lot of products coming together. So each one should minimize their overhead.
Give our product a go and let us know what you think?