Some notes and tools for reverse engineering / deobfuscating / unminifying obfuscated web app code.
I'm writing this post to publicly come out as trans (specifically: I wish to transition to become a woman).
This post won't be as polished or edited as my usual posts, because that's kind of the point: I'm tired of having to edit myself to make myself acceptable to others.
I'm a bit scared to let people know that I'm trans, especially because I'm not yet in a position where I can transition (for reasons I don't want to share, at least not in public) and it's really shameful. However, I'm getting really
| import * as k8s from "@pulumi/kubernetes"; | |
| import { streamInvoke } from "@pulumi/pulumi/runtime"; | |
| import * as pulumi from "@pulumi/pulumi"; | |
| // Install the sealed secret controller. | |
| new k8s.yaml.ConfigFile("sealed-secret-controller", { | |
| file: "https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.12.4/controller.yaml", | |
| }) | |
| // Create a SealedSecret. |
| defmodule MyApp.Factory do | |
| use ExUnitProperties | |
| alias MyApp.{Repo, User, Comment} | |
| ### Generators | |
| def generator(:user) do | |
| gen all name <- string(:alphanumeric, min_length: 2), | |
| email <- generator(:email), | |
| age <- integer(10..130) do |
| // I'm suggesting we add a new "adopt X from <Y />" syntax to the JSX language | |
| // it would de-sugar to render prop children, but look and read better than | |
| // what we currently have. For example: | |
| // 1. | |
| // this sugar | |
| function MyComponent(props) { | |
| adopt foo from <Bar />; | |
| return <div>{foo}</div>; | |
| } |
| // This is @zz85's attempt to understand and annotate the greenlet.js lib | |
| // from https://github.com/developit/greenlet/blob/master/greenlet.js | |
| /** Move an async function into its own thread. | |
| * @param {Function} fn The (async) function to run in a Worker. | |
| */ | |
| export default function greenlet(fn) { // greenlet takes in a function as argument | |
| let w = new Worker( // creates a web worker | |
| URL.createObjectURL( // that has a local url | |
| new Blob([ // created from a blob that has the following content |
I wrote this answer on stackexchange, here: https://stackoverflow.com/posts/12597919/
It was wrongly deleted for containing "proprietary information" years later. I think that's bullshit so I am posting it here. Come at me.
Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?
Warning: These views are highly oppinated and might have some slightly incorrect facts. My experience with typescript was about 2 weeks in Node and a week in angular2.
TypeScript is implementing their own take on JavaScript. Some of the things they are writing will likely never make it in an official ES* spec either.
Technologies that have competing spec / community driven development have a history of failing; take: Flash, SilverLight, CoffeeScript, the list goes on. If you have a large code base, picking TypeScript is something your going to be living with for a long time. I can take a bet in 3 years JavaScript will still be around without a doubt.
Its also worth noting that they have built some things like module system and as soon as the spec came out they ditched it and started using that. Have fun updating!
| global !p | |
| def first_blank_line(): | |
| """ Search current vim buffer for first blank line. If not found return current line """ | |
| b = snip.buffer | |
| index = 0 | |
| break_index = 100 | |
| com_delim = re.compile(r'^(\s+)?(""")') | |
| in_comment = False | |
| for line in b: | |
| index += 1 |